zos_jobs: Return error to user instead of throwing exception

[john-craig]

Is your feature or enhancement request related to a problem or limitation? Please describe

Currently most zos_jobs functions (e.g. delete_job and get_job_status) throw a RequestError if they are performed against a job name and job ID combination that does not exist. This is pretty inconvenient and should probably just be part of the data returned to the user.

Describe your enhancement idea

Return information about the job that was not found to the in the function response instead of throwing an error.

Describe alternatives you've considered

I have tried catching the error, however at some layer there are still stacktrackes leaking into stderr, which I would really rather not have to look at. I've actually a couple of different methods of suppressing these messages, and none have worked.

Provide any additional context

This is from a tool that is running as a command line interface.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[JTonda]

Research:

• Verify whether or not error message is clear
• Stack traces or error information is not automatically output to stderr