docs: Update input schema specs

[jancurn]

No description provided.

[TC-MO]

Suggested change

	To define an input schema for an Actor, set `input` field in the `.actor/actor.json` file to an input schema object as described below, or path to a JSON file containing the input schema.
	For backwards compability, if the `input` field is omitted, the system looks for an `INPUT_SCHEMA.json` file in the `.actor` directory or for an `INPUT_SCHEMA.json` file in the Actor's root directory - but do not depend on this behavior as it might be removed in the future.
	To define an input schema for an Actor, set `input` field in the `.actor/actor.json` file to an input schema object as described below, or path to a JSON file containing the input schema.
	For backwards compatibility, if the `input` field is omitted, the system checks these locations:
	1. `INPUT_SCHEMA.json` in the `.actor` directory
	2. `INPUT_SCHEMA.json` in the Actor's root directory

I would omit any information about what might or might not happen, if it does then we can update the documentation with a note. If we want to steer users in one direction we can add that some info about preferred or recommended way of doing things

[jancurn]

IMO it's quite normal in docs to say that some behavior might be deprecetated in the future, so that people don't use it - this is exactly the case

[TC-MO]

In my experience with docuemntation, I've never seen a message with possibility of depreacation. It was always with specific end-of-life dates.

If we want to guide users towards a preferred implementation I would advise to explicitly mention which way is recommended.

[jancurn]

Really? I see it all the time in docs that some feature is deprecated and might be removed in the future. See https://www.google.com/search?q=deprecated+and+might+be+removed+in+the+future

[TC-MO]

But none of the results are from official documentation but rather community resources.

Furthermore
deprecated & might be removed in the future =/= might be removed in the future,
if the intention is that these two ways of defining input schema are deprecated and & will be removed in the future, then let's mark them explicitly as deprecated and then mentioning that they might be removed in the future is a-ok

[jancurn]

Oh right, fair enough, I'll mention it's deprecated