Update the `apollo` command for better compatabiliy with the chat APIs

Make openfn apollo global_chat work nicely. This steps away from the generic apollo command and adds logic specific to particular services.

This should make it possible to call apollo chat for testing and debug without needing a lightning UI (which would be super useful right now)

• Maybe accept a session object or name, which maintains history across several chats
• Maybe accept payload arguments like --@content "is this the way to amaraillo" to make it easy to configure payload keys without having to attach a JSON object (is this easier or harder??)
• Make sure the chat message is nicely formatted
• Consider serializing attachments to disk for easy compatibility, ie, write out workflow.yaml
• Add an option to print metadata context, like rag results or tool usage

Start at the openfn apollo global_chat entry point and compare it with the generic apollo command and Lightning UI behavior. Clarify the desired session handling, payload arguments, message formatting, attachment serialization such as workflow.yaml, and metadata output before defining completion criteria.