feat: evolve Kangaroo visual approach

[Fupete]

We need to evolve the kangaroo design.

To do

• ✅ From the usability test: switch sides (left-right) between the drop-down quicklinks menu and the metadata informations. We need then to evaluate the approach and scalability at different levels;
• 👎 or 🤔 evaluate the possibility of moving the "Parliamo di" tags to the end of the page content;
• ✅ evaluate chances to hide some information with a toggle approach (show/hide);
•  ✅ enhance show quicklinks menu with a btn-outline approach
• 🤔 code: split News and Events Kangaroos from the other ones
  • 🤔 content: maybe we need to change personalInfo props on all the news to a dedicated newsInfo...
• 🤔 code: we need to evaluate a complete refactoring of these meta handling if we want to be able to improve an horizontal layout
• ...

Results at the moment

1st level

2nd level (risorse per progettare/fase)

### 3rd level (kit)

4th level (kit action)

3rd level (DS/Scheda contenuto)

3nd level (news)

3rd level (event)

[github-actions]

⚡ Lighthouse report for the home page 🏠

Category	Score
🟠 Performance	63
🟢 Accessibility	100
🟢 Best practices	100
🟢 SEO	100

See the full report...

Other pages

• /progetto/ 🟠 80 🟢 100 🟢 100 🟢 100
• /norme-e-riferimenti/linee-guida-di-design/ 🟠 81 🟢 100 🟢 100 🟢 100
• /design-system/componenti/ 🟠 80 🟢 100 🟢 100 🟢 100

[Fupete]

@astagi I need a code review

@danielaiozzo @pedromaria88 @zetareticoli @danielenole @gianvitofanelli I need a visual/content review. Please navigate each level of page content (1st, 2nd, kits, actions, news, events, ds, ...) to understand this new kangaroo approach.