Improved Type Safety in Python Client API

[Itssshikhar]

Description

This PR improves the type safety of the Python client API by ensuring consistent TypedDict usage across all service clients. This makes the API more predictable.

Changes

• Verified and maintained proper TypedDict definitions across all service clients
• Ensured consistent typing patterns across the codebase
• Fixed linting issues to maintain code quality
• Verified all tests pass with the typing improvements

Testing

• ✅ Ran make format for code formatting
• ✅ Fixed all linting issues with ruff
• ✅ Ran make test to verify functionality
• ✅ Verified type checking with mypy

Related Issues

Closes #32

[codekansas]

awesome :) could you fix the failing unit tests? otherwise looks good!

[Itssshikhar]

thanks @codekansas . I just fixed the failing unit tests and pushed it.

[WT-MM]

Awesome, this looks really good! Just a few nitpicks to satisfy my ocd

[Itssshikhar]

@WT-MM Hope this helps :)

[WT-MM]

okay, actually after taking another look at this again, can we keep the protobuf return types if they're typed or use dataclasses?

Being able to access values as attributes is probably more ergonomic (e.g. getting response.states instead of response["states'])

Otherwise, it's probably ready to merge in - I'll resolve conflicts and merge in afterwards

[Itssshikhar]

@WT-MM you are right. Having access to the values as attributes is better.
I'll take a look at it.