`apify call` to support input passing

[mtrunkat]

Call operations needs to support the input passing. Having a CLI that can't do the main action of the platform - to run an Actor - is quite sad 😢. We could implement it as --input=@data.json param, as per the https://github.com/apify/actor-specs?tab=readme-ov-file#cli-5

-- From Slack.

[B4nan]

@vladfrangu let's first finish with the other open things, assigning you here as now you are the new CLI overlord :]

It's not a priority, I'd first like to see the input schema support in SDK, but on the other hand, it sounds like a pretty simple task.

[netmilk]

Hi,

I have a little +1 here. I'd love to invoke parametrized runs from the CLI the *nix way. Related to that, it would be awesome to retrieve the run ID in a machine-readable way.

I'd love to start adding badges to the README.md like the one above, but it doesn't make any sense If I can't run the Actor with custom parameters and then process the output when it's done. More examples if the apify-badger

Example:

$ echo "netmilk n1k" | jo -a | jo usernames:=- | \
apify call netmilk/sherlock --save-run-id=run_id.txt && cat run_id.txt
RqSxZh0EBsiA9WGZK