Extra attributes from the server class,role

## Summary of the bug

This may be something to do with next.js and not belong here but its a pretty annoying error that spams the developer console.

## 🪜 How to reproduce
Tell us the steps to reproduce the problem:
1. See code below
2. Refresh the page a few times and look at dev console

## 📸 Screenshots or code

Simplest code that fairly reliably reproduces it, if you remove the SVG it triggers less often but it still triggers
```tsx
export default function PageInner() {
return (
<>






Get started
Get started2

)
}

```

## 🖥 📱 Device
- Type: Desktop
- Device: [Macbook
- OS version: macOS Sonoma
- Browser version: Chrome 130

## 🧐 Expected behaviour
No console error

## 📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.

*Given*
*When*
*Then*

## Additional info
Tell us anything else useful to help us fix or understand the problem.

Start by reproducing the reported console error with the TSX example in a Next.js environment, using the supplied refresh steps and Chrome. Inspect which component or rendering boundary produces the extra class and role attributes; done means repeated refreshes no longer produce the console error for the example.

Written by the indexing model from the issue text.