refactor: change to complex objects instead of raw dictionaries

[avelino]

This commit introduces a significant architectural change in how we handle API responses. Instead of working with raw dictionaries, we now use proper model classes (Charge, CardToken, Refund, etc.) to represent API resources.

Key changes:

• Created new models.py file with proper data classes for all API resources
• Updated client methods to return typed objects instead of dictionaries
• Modified examples to demonstrate usage with new object-oriented approach
• Updated tests to work with new model classes
• Added type hints throughout the codebase

This change brings several benefits:

1. Better type safety and IDE support
2. More intuitive API with proper object methods
3. Easier validation and data manipulation
4. Improved code maintainability
5. Better documentation through type hints

The change is backwards compatible as the model classes can still be accessed as dictionaries through their attributes.

[Copilot]

Copilot reviewed 5 out of 7 changed files in this pull request and generated 1 comment.

Files not reviewed (2)

• examples/basic_usage.py: Evaluated as low risk
• tests/test_client.py: Evaluated as low risk

Comments suppressed due to low confidence (2)

barte/models.py:41

• The from_dict method in Charge class modifies the input data dictionary directly. Create a copy of the dictionary before modifying it.

def from_dict(cls, data: Dict[str, Any]) -> "Charge":

barte/models.py:69

• The get_qr_code method in PixCharge class directly modifies the instance attributes. Return a new instance with the updated attributes to maintain immutability.

def get_qr_code(self) -> "PixCharge":