fix: allow SDK to handle the Horde rc

[db0]

When returning errors, the horde now also sends back an rc along with the message. This appears to cause the SDK to barf

horde_sdk.ai_horde_api.exceptions.AIHordeRequestError: The response type doesn't match expected one! See `object_data` for the raw response.

This is an attempt to handle the rc returned.

[tazlin]

Errors are handled differently because the API didn't publish (in the api docs) the 'message'-style responses. With the latest 'rc'-style error messages, this represents a fairly significant upset to the way this needs to be handled on the sdk side, especially considering it's going to cause errors to propagate to the worker.

Did you test the rc changes to the API with the sdk at all, or this change to the sdk?

[db0]

Well no, because the API didn't change. This is just an addition of an extra key on errors. I keep forgetting how strict the SDK is. The erros didn't change. the "message" should still be there.

[tazlin]

The API did change - and pretty significantly. This "message" behavior is an emergent "feature" of the API which I was forced to cope with as a client. In many places, you don't publish the response or response code, and simply return a json string containing that field. Further, if I recall correctly, there are at least some models which also contain 'message' as a field. As a client, using object models, I can't determine which model to coerce the API's json response to given that reality without introducing some sort of check - in this case, that it only contains 'message'.

The API is supposed to be a contract. I can't foresee the future and expect these sorts of changes. For better or for worse, the SDK is inextricably tied to the worker at this time, so I expect that if you make API changes to this effect - at a minimum - the worker is checked against those API changes for backward compatibility.

[db0]

You don't need to scold me dude. It's not a huge deal. In any case, you now have a way to determine actual errors. but I'm not sure where you think I don't return a response code. I don't even think that's possible with http protocol

[tazlin]

Superseded by another pull request.