[Feature] [Studio]: add two-column resume layouts and improve section visibility controls

[Gautam25Raj]

Summary

This pull request enhances the resume editing experience by introducing support for two-column resume layouts and improving section visibility management. It also resolves issues #136 and #137, addressing layout customization and section display behavior within the resume editor.

What's Changed

Resume Editor Enhancements

• Added support for two-column resume layouts to provide greater flexibility in resume design and content organization.
• Improved section visibility controls for a more intuitive editing experience.
• Enhanced editor behavior to better reflect section visibility preferences in real time.

User Experience Improvements

• Improved layout customization options for users building modern and space-efficient resumes.
• Refined section management workflows to make it easier to control which content appears in generated resumes.
• Improved consistency between editor configuration and resume preview rendering.

Linked Issues

• Fixes [FEATURE]: Locked Contact Header with Conditional 2-Column Template Toggle #136
• Fixes [FEATURE]: Actions Dropdown Menu on Dashboard Overview Recent Cards #137

Notes

• No breaking changes are introduced.
• These improvements provide greater control over resume presentation while enhancing the overall editing experience.

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.