[Feature] [Portfolio] Introduce portfolio management, templates, and publishing infrastructure

[Gautam25Raj]

Summary

This PR introduces the foundation of the portfolio platform, including portfolio management workflows, template rendering systems, content structures, publishing support, and state management infrastructure.

The update establishes the core architecture required for creating, managing, rendering, and publishing portfolios across the ecosystem.

Features

Portfolio Platform Foundation

• Added portfolio site configuration with environment-aware URLs
• Implemented backend API URL handling for:
  • Public access
  • Internal access
• Established core portfolio application architecture

Portfolio Content Management

• Added portfolio content structure and default content models
• Introduced default portfolio templates
• Added local storage support for portfolio draft management
• Improved content persistence workflows

Portfolio Templates & Rendering

• Integrated portfolio templates into the rendering system
• Added portfolio rendering logic and template support
• Improved consistency across content rendering workflows

Portfolio Publishing

• Added published portfolio fetching support
• Implemented caching for published portfolio content
• Improved public portfolio loading and delivery performance

Improvements

State Management

• Added Zustand store for portfolio state management
• Improved client-side data handling and synchronization
• Established scalable portfolio state architecture

Studio Integration

• Updated Studio navigation to include portfolio access
• Improved navigation consistency across ecosystem applications

Developer Experience

• Configured TypeScript support for the portfolio application
• Added Vitest configuration and testing support
• Improved development workflow consistency

Testing

• Added tests for:
  • Portfolio content contracts
  • Portfolio rendering workflows
• Improved platform reliability and maintainability

Notes

• No breaking changes
• Introduces the initial portfolio platform architecture and publishing workflows
• Establishes the foundation for future portfolio features and enhancements

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.