feat: Add production-ready Kubernetes deployment pipeline and financial integrations

[yoanyombapro1234]

Summary

This PR adds a comprehensive production deployment pipeline and extensive financial automation capabilities:

Deployment Infrastructure

• Production-ready Kubernetes deployment pipeline with GitHub Actions
• Helm templates and production values configuration
• Comprehensive deployment documentation (DEPLOYMENT.md, SECRETS-SETUP.md)
• Automated CI/CD workflows for production deployments

Financial Integrations

New integrations added:

• Plaid: Bank account linking, transaction categorization, balance retrieval, recurring payment detection
• QuickBooks: Complete accounting operations including invoices, bills, payments, customers, vendors, and financial reporting
• FreshBooks: Client management, time tracking, invoicing, expense management, payment recording
• Xero: Invoice creation, bill management, bank reconciliation
• Enhanced Stripe: Revenue analysis, failed payment detection, tax reporting, payout reconciliation

Financial Automation Templates

• Cash flow monitoring
• Expense approval workflows
• Late invoice reminders
• Monthly financial reports
• Stripe-QuickBooks reconciliation

Technical Improvements

• Financial validation utilities
• OAuth flow implementation
• Database schema for financial sync
• Comprehensive TypeScript type definitions for all financial services
• Test utilities for financial tools

Configuration

• Updated environment variables for new integrations
• Production-critical secrets configuration
• Enhanced configuration management

Test Plan

• [x] Deployment pipeline workflows validated
• [x] Financial integration tools implemented with proper error handling
• [x] TypeScript types and schemas defined
• [ ] End-to-end testing of financial automation templates
• [ ] Production deployment validation

🤖 Generated with Claude Code

[greptile-apps[bot]]

Skipped: This PR changes more files than the configured file change limit: (149 files found, 100 file limit)

[vercel[bot]]

@yoanyombapro1234 is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	898826469cd3930a32de07c36437795f62d3f8c4	apps/sim/.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}