[Feature] Add portfolio cache management, validation schemas, and views tracking

[Gautam25Raj]

Summary

This PR introduces portfolio cache management utilities, expands validation coverage across billing and portfolio workflows, and adds scalable views tracking infrastructure for portfolios and share links.

The update also improves database performance configuration and strengthens platform-level data integrity.

Features

Portfolio Cache Management

• Added invalidatePublicPortfolioCaches utility
• Added revalidatePublicPortfolios utility
• Improved public portfolio cache invalidation workflows
• Enhanced cache consistency for published portfolio content

Portfolio Validation

• Added portfolio validation schemas for:
  • Portfolio content
  • Portfolio drafts
• Improved data integrity and validation coverage
• Enhanced validation consistency across portfolio workflows

Billing Validation

• Added Zod validation schemas for:
  • Checkout requests
  • Billing webhook events
• Improved validation reliability for billing-related operations

Views Tracking System

• Implemented views tracking for:
  • Public portfolios
  • Share links
• Added Redis-backed buffering and flushing workflows
• Improved scalability and tracking efficiency for analytics events

Improvements

Database Performance

• Enhanced Prisma database connection configuration
• Improved connection handling and performance characteristics
• Optimized database interaction reliability

Slug Validation

• Updated slug validation rules
• Added additional reserved usernames
• Improved protection against routing and namespace conflicts

Testing

• Added test coverage for:
  • API key validation
  • Flexible authentication middleware
  • Billing webhook processing
  • Portfolio validation workflows
• Improved reliability and maintainability across core systems

Notes

• No breaking changes
• Focused on validation reliability, analytics infrastructure, and portfolio platform performance

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.