Fix: deserialize ignores new fields

[majesticio]

This introduces a modification to the deserialization logic within the Python client to gracefully handle unexpected fields in the API responses. As we've observed the current implementation raises a TypeError when it encounters any unexpected keyword arguments during the initialization of response objects.

This approach leverages the class's annotations attribute, which contains a dictionary of expected fields based on type annotations. We can filter for fields that match the annotations.

I have also included a test in tests/test_shared_responses.py to ensure that it functions as expected.