Exception creation, new testing, raising exception in retrieve, Fixes #3212

[alextemn]

Changes being requested

-Adding response error to exception class mapping for async calls
-Creating exception from error response
-Raising an exception when status is "failed" or "incomplete"

What to keep in mind

• Async jobs still return 200s, but we return appropriate exceptions
• If we want status codes to return the appropriate code, we'd need to make other, more upstream changes
• It also seems like synchronous jobs have the same issue of only returning 200s, since the server still gets back to us that there was an error, but I'm unsure if appropriate exceptions are raised, or if thats needed. I can open a new issue on this if needed

Additional context & links

#3212
fixes #3212

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 76bd1aaaf6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".