ObjectNotFound does not get risen, when the request returns a 404

[DebVortex]

Currently, durga only raises a ObjectNotFound exception, when the API returns a valid but empty response, when the get function of the collection is called. An API may also return a 404, which causes durga to try to decode non existing JSON.

[keimlink]

Thanks for the bug report @DebVortex! We have to decide how to handle this problem.

1. Raise an ObjectNotFound exception
2. Same as 1. but add the response object to the exception as an attribute
3. Raising an HTTPError using the raise_for_status() method provided by requests, which will contain the request and response objects

[DebVortex]

I would vote for option 3.