Add comprehensive API models for graph tiers and service offerings

[jfrench9]

Summary

This PR significantly enhances the robosystems client by introducing comprehensive data models for graph tiers and service offerings, along with improved response handling for related API endpoints.

Key Accomplishments

New Data Models (22 new model classes)

• Graph Tier Models: Complete model hierarchy for graph subscription tiers, including tier info, limits, backup configurations, copy operations, and instance management
• Service Offering Models: Comprehensive models for service offerings, repository plans, and rate limiting configurations
• Pricing & Operations: Detailed models for operation costs, token pricing, AI operations, and storage pricing structures
• Response Containers: Structured response models for available graph tiers and service offerings endpoints

API Enhancements

• Updated get_available_graph_tiers endpoint to use new structured response models
• Enhanced get_service_offerings endpoint with improved response handling
• All new models properly registered in the models module for seamless integration

Model Features

• Full support for graph subscription management and tier-based limitations
• Comprehensive pricing model support including overage pricing and included quotas
• Detailed repository plan configurations with rate limiting capabilities
• Storage information models with tier-based allocations

Breaking Changes

⚠️ Potential Breaking Changes: The response structure for graph tiers and service offerings endpoints has been enhanced with new model classes. Existing code that directly accesses raw response data may need updates to use the new structured models.

Testing Notes

• Verify that existing API calls to graph tiers and service offerings endpoints continue to work
• Test model serialization/deserialization with real API responses
• Validate that all new model relationships and nested structures function correctly
• Confirm backward compatibility for existing client usage patterns

Infrastructure Considerations

• This change significantly expands the client's model layer (+2000 lines of new model code)
• Enhanced type safety and IDE support through structured models
• Improved maintainability through organized model hierarchy
• Models follow established patterns for consistency with existing codebase

---

🤖 Generated with Claude Code

Branch Info:

• Source: refactor/api-models-improve-2
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com