Liisa/enhancement/627 site wide bugs and UI improvements

[davylis]

📄 Pull Request Overview

Closes #627

🔧 Changes Made

1. Updated multiple UI components and styles to improve layout consistency and responsiveness across the site. This includes:

• refining share button, footer rights, join-us icon hover, and news page spacing/styles
• stabilizing z-index for the scroll-to-top button
• improving feedback card sizing so inputs and buttons use responsive widths
• adjusting Team Header With Mosaic spacing by replacing the old desktop spacer approach with balanced left/right padding
• removing the chatbot toggle from the root layout

2. Refactored presentation package section typing and data shape:

• fixed image and sidebarLogo to structured objects with src, alt, width, and height
  -updated createSection, related types, and section data to match the new structure

3. Improved image handling in news-related components by updating image dimensions.

4. Cleaned up legacy feedback styling by commenting out the old feedback card.

---

✅ Checklist Before Submission

• Functionality: I have tested my code, and it works as expected.
• JSDoc: I have added or updated JSDoc comments for all relevant code.
• Debugging: No console.log() or other debugging statements are left.
• Clean Code: Removed commented-out or unnecessary code.
• Tests: Added new tests or updated existing ones for the changes made.
• Documentation: Documentation has been updated (if applicable).

---

📝 Additional Information

Provide any additional context or information that reviewers may need to know:

• All needed done

[Rutjake]

Great work! Most of the bugs have been fixed, and the overall user experience of the site is improving significantly. However, a few things still need attention:

Mobile Responsiveness: The pages are still too wide for mobile screens. You can see this when "swiping" the mobile view sideways and the page wobbles horizontally.

GameArt Page: This page still crashes in the local development environment, as we discussed earlier on Discord.

See also the comments below.

[Rutjake]

We could have deleted this, but we can leave it in for a quick rollout, just in case it's needed later.

[Rutjake]

Regarding the commented-out code: we should avoid leaving unused components commented out as it adds technical debt. It's better to either keep the component active or remove it entirely. Since we have a dedicated issue coming up for cleaning up old components, let's not leave it in a commented state—could you either revert the commenting or delete the file?