Cloud Connector abstractions
As we've moved from a single CC feature (Code Suggestions) to 2+ (Chat and beyond), I see code quality in the monolith suffer due to: - Lack of coding abstractions when dealing with access tokens - Duplication of switching logic and too many SaaS vs SM checks - Inconsistent placement of CC helpers (`Ai` vs `CloudConnector` namespaces) We should go over existing code and learn from how other teams have implemented our auth solution, and create better abstractions around it.
epic