Refactor billing API and remove deprecated connection/view endpoints

[jfrench9]

Summary

This PR implements a significant refactoring of the robosystems client by updating billing API status handling and removing deprecated connection and view management functionality. The changes streamline the codebase by eliminating unused endpoints and consolidating subscription-related models.

Key Accomplishments

• Updated Billing API: Refactored checkout status endpoint with improved status value handling
• Removed Connection Management: Eliminated entire connections API module including:
  • Connection CRUD operations (create, get, delete, list)
  • OAuth flow endpoints (init, callback, token exchange)
  • Link token management
  • Connection synchronization
• Removed View Management: Deleted view creation and management endpoints
• Model Cleanup: Removed 30+ obsolete model classes related to connections and views
• Subscription Model Updates: Consolidated graph subscription models and simplified tier management

Breaking Changes

⚠️ This is a breaking change - The following functionality has been completely removed:

• All connection management APIs (/connections/* endpoints)
• View creation and management APIs (/views/* endpoints)
• Related model classes for connections, OAuth flows, and view configurations
• Provider-specific configurations (Plaid, QuickBooks, SEC)

Applications using these endpoints will need to be updated before upgrading to this version.

Files Impacted

• Modified: 6 files (billing API + subscription models)
• Deleted: 55 files (connections, views, and related models)
• Total: 61 files changed

Testing Notes

• Verify billing checkout status API continues to function with updated status handling
• Confirm subscription-related functionality works with consolidated models
• Test that removal of connection/view endpoints doesn't impact other API functionality
• Validate that import statements across the codebase have been properly updated

Infrastructure Considerations

• This change significantly reduces the client library footprint
• Applications should verify compatibility before deploying
• Consider versioning strategy for clients that still require connection/view functionality
• Monitor for any residual dependencies on removed models in downstream services

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/improved-checkout
• Target: main
• Type: feature

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