Output and errors standardization

[RobotSail]

Errors for copilot-ops should be well-defined and explicit so that the user does not receive unambiguous responses.

For example, if copilot-ops exceeds the maximum response length for a request, the user should know that this was the cause of error.

[guymguym]

The plan is:

• errors.go - add ErrorToUser/WarningToUser functions which will keep a list of those errs and warnings, also log it and return an error interface for the caller to return back.
• call these functions in the other packages cmd/filemap/opensai/etc when we identify it and make sure the message provides a usable info for the end user (not the bot framework, but the user providing the input itself).
• patch.go we need a finally case so that it will output the errors and warnings collected.

[guymguym]

We have output type flag supporting json vs plain.
We have Filemap.EncodeToInputTextFullPaths(outputType).
We want to pull up the output type handling so it covers both output and errors.
We want that for the bot to have a machine readable output both for errors and generated/edit content.