[Refactor] Unify resume sections using GenericCustomSection architecture

[Gautam25Raj]

Summary

This PR refactors multiple resume editor sections to use a shared GenericCustomSection component, significantly reducing code duplication and improving maintainability across the resume editing system.

The update also improves state management consistency, saving workflows, and type safety across template-related systems.

Refactor

Generic Section Architecture

• Replaced individual implementations for:
  • Awards
  • Certifications
  • Interests
  • Languages
  • Publications
  • References
  • Volunteer
• Introduced shared GenericCustomSection component
• Unified rendering and interaction behavior across custom sections
• Reduced duplicated logic and component complexity

State Management

• Updated state handling to align with the new shared section structure
• Simplified event handling workflows across resume sections
• Removed unnecessary state management hooks from legacy section implementations

Toolbar & Saving

• Updated ToolbarSecondaryActions to use the latest useResumeStore saving workflow
• Improved save consistency and editor integration behavior

Type Safety

• Enhanced template registry type definitions
• Improved type safety and maintainability across template systems
• Refined shared typing consistency for section rendering

Improvements

Maintainability

• Simplified section architecture and internal organization
• Improved scalability for adding future custom sections
• Reduced component fragmentation and duplicated logic

Consistency

• Improved rendering consistency across all shared resume sections
• Unified state and interaction patterns
• Enhanced editor workflow reliability

Beta Status

✅ Stability Improvements

• Resume section architecture is now more centralized and maintainable
• Shared rendering flows are more consistent

Notes

• Focused on maintainability, scalability, and shared section architecture
• Additional resume editor improvements expected in future beta releases

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.