[Refactor] Improve template document type handling and dynamic filtering system

[Gautam25Raj]

Summary

This PR refactors the template browsing and rendering architecture to improve document type handling, dynamic filtering, layout statistics, and template metadata consistency across the templates experience.

Refactor

Template Filtering

• Updated TemplateFilters to dynamically generate:
  • Family options
  • Layout options
• Improved filtering flexibility based on provided template data
• Enhanced scalability for future template categories and layouts

Template Components

• Updated TemplateGroup to consume TemplateSummary directly
• Added improved group information rendering and metadata display
• Enhanced TemplateHeader with richer template detail representation
• Refactored TemplatesHeader to include:
  • Document type summaries
  • Improved layout statistics
  • Better overview presentation

Template Data Structure

• Refined template configuration structure in:
  • config/templates.ts
• Added additional metadata support
• Improved type safety and shared template consistency
• Enhanced maintainability for template registry handling

Improvements

Routing & URL Handling

• Updated utility functions for improved href generation
• Fixed link generation in TemplatesPreview
• Improved document type routing consistency across templates

UI & Information Architecture

• Updated TemplatesPortalPage with improved document type presentation
• Enhanced layout organization and template information clarity
• Improved browsing experience and template discoverability

Maintainability

• Simplified shared template handling workflows
• Improved consistency across template-related utilities and components
• Enhanced scalability for future template system expansion

Notes

• No breaking changes expected
• Focused on template architecture, filtering flexibility, and document type consistency

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.