Refactor web analytics to use Rybbit instead of Umami

[BramSuurdje]

✍️ Description

This pull request updates the analytics integration in the frontend application. The main changes involve switching the analytics script to use the new API endpoint and updating the analytics token, along with a minor import adjustment to support the new script loading method.

Analytics integration updates:

• Replaced the direct <script> tag for analytics in the RootLayout component with the Next.js <Script> component, loading the script from the /api/script.js endpoint and updating the attribute from data-website-id to data-site-id. The script now loads after the page becomes interactive. (frontend/src/app/layout.tsx)
• Updated the analytics token from "aefee1b9-2a12-4ac2-9d82-a63113edc62e" to "f9eee289f931" in the analytics config object. (frontend/src/config/site-config.tsx)

Codebase maintenance:

• Added the next/script import to support usage of the <Script> component. (frontend/src/app/layout.tsx)

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.