Make all components with English text functional client components

[danielhjacobs]

This unlocks client-side translations (#358) and will be necessary whether we use next-export-i18n or custom translation code. I feel like no one wants to accept #358 yet, but doing this first can make the commits there a lot cleaner.

[danielhjacobs]

Why this will be needed:

Assuming we want to keep serving the website client-side, the website language needs to be checked client-side in order to apply translations. That means changing the language needs to, in some way, be done by JavaScript. next-export-i18n has two ways to do that: check the window.location.search or window.localStorage, and as window is only available client-side, either way it will only work on client components. Therefore, every component with English text (including the header and footer) needs to be a client component.

[danielhjacobs]

For a draft with translations that build upon this, see danielhjacobs#4

[torokati44]

Since the current website was mostly your work originally, do you think you could spare some minutes to review this, @Dinnerbone? Only if your time and energy allows it, of course!

[danielhjacobs]

Of note is there's something, previously discussed on Discord, that should probably be done to improve the performance of this, specifically when it comes to the compatibility and AVM2 compatibility pages. Namely, the avm2-report should be copied to the website's static files folder (https://github.com/ruffle-rs/ruffle-rs.github.io/tree/master/public) in a pre-build step, instead of using the new fetch-report route.

The two places with const reportReq = await fetch("/compatibility/fetch-report"); can then const reportReq = await fetch("/avm2-report.json"); instead.

Edit: Done