feat: implement responsive NavBar component with Sidebar navigation

[idris999-c]

Pull Request

📄 Summary

This PR implements a fully functional, responsive NavBar component and enhances several core UI components to ensure a seamless mobile navigation experience and technical stability.

Key Contributions:

• NavBar Component: Implemented using Svelte 5 runes and DaisyUI. Features multi-size support (xs to lg), visual variants (glass, transparent, solid), and flexible layout snippets.
• Enhanced Mobile Experience:
  • Integrated Sidebar (Drawer) for navigation links on small screens.
  • Implemented responsive search (icon dropdown pattern on mobile).
  • Cleaned up mobile UI by removing unwanted hover/active backgrounds on the menu trigger.
• Refined Core Components:
  • Drawer: Fixed a critical z-index and positioning bug (z-20, relative) to ensure sidebar links are clickable.
  • Menu: Optimized internal class mapping to support responsive navigation items within the sidebar.
  • Text: Standardized property usage for consistent branding visibility across themes.
• Storybook Excellence:
  • Refactored all stories to manual rendering, eliminating the "dual NavBar" bug and ensuring absolute isolation on the Autodocs page.
• Technical & Compliance:
  • Added mandatory SPDX license headers (REUSE compliance) to all new files.

---

🧩 Affected Modules

• Source Code
• Documentation
• CI / Infra

---

✅ Checklist

• My branch name follows format: feat/add-navbar-component
• My PR title starts with one of the approved types (feat:)
• My code is formatted according to project standards
• I ran static analysis (pnpm check, pnpm lint) and resolved warnings
• I ran tests successfully via Storybook verification
• I updated/added Storybook stories with manual rendering isolation
• I ensured this PR has no unrelated changes
• This PR is ready for review

---

🔗 Related Issues

Closes #361

[husamettinarabaci]

LGTM