feat: implement tab-based navigation for roadmap sections

[CapThunder19]

Summary

This PR introduces tab-based navigation for the roadmap sections (Planned, In Progress, and Done) to improve readability and reduce excessive vertical space usage.

Previously, all roadmap sections were displayed simultaneously, which caused the Done section to occupy significant space and made the roadmap harder to navigate. With this update, users can switch between sections using tabs, resulting in a cleaner and more organized interface.

Changes Made

• Implemented tab navigation for:

  • Planned
  • In Progress
  • Done

• Displayed only the selected roadmap section at a time

• Improved layout clarity and reduced vertical scrolling

• Maintained existing roadmap content structure

• Ensured consistent UI styling with the current design

Related Issues

Closes #480

[github-actions]

Thanks for your first PR! A maintainer will review it shortly.

Make sure CI passes and take a look at our contributing guide if you haven't already.

[ShiraiEd]

Hi, thank you for the contribution!

Can you add one more navigation tab named like "All" that returns to the Rolling Roadmap?

Also, there is a conflic in docs/templates/roadmap.html, resolve that so we will be able to merge this pr pls

[CapThunder19]

pls review it

[ShiraiEd]

This is very clean overall, it is working well,

just a concern, the way this is structured now makes each new change on the content cards mandatory in both roadmap.html and roadmap-section.html , otherwise the data would be inconsistent,
For this a cleaner approach would be to extract each section's card into Zola shortcodes
like shortcodes/roadmap_planned.html and them call them from both the templates,
this way the we will need to update the content in one place, reducing the risk of potential confusion.

Minor nit

.column-footer is very generic, future updates could cause collisions, something more specific like .roadmap-column-footer would be safer.