chore: update docusaurus to 3.X

[jonas-jonas]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Waiting for the first build to start…

[vinckr]

lgtm :)
looked through most pages

[aeneasr]

I didn't look at the 60k lines changed but browsed a few pages and they look good to me. Did you check that there are no page speed or SEO issues?

[jonas-jonas]

@aeneasr most of that is package-lock.json:

Performance is a little worse on the preview env, but that might be due to it being a preview env, SEO is 100%.

[aeneasr]

Yeah, preview env is always a bit slower