Upgrade docusaurus and preset version

[jinhojang6]

• Upgraded Docusaurus to version 3.8.1
• Upgraded Logos preset (theme) to version 1.0.3-beta.11
• Fixed content issues that did not follow Docusaurus’ markdown format

Sorry for the delayed updates, I had to manually resolve some conflicts between the content and Docusaurus versions.

Examples:

• Updated links to follow Docusaurus' markdown format (e.g., changed <https://docs.waku.org/> to [https://docs.waku.org/](https://docs.waku.org/))

• Removed node fetch-content.js from the build commit due to incorrect formatting in the remote repo (e.g., <4 minutes to synchronize)

• Added missing Tabs and TabItem imports:

  import Tabs from '@theme/Tabs';
  import TabItem from '@theme/TabItem';

To merge this PR, we need to resolve the issue with the source content first: logos-messaging/research#117

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-waku-org	❌ Failed (Inspect)			Jul 27, 2025 2:22pm

[jinhojang6]

Staging: https://docs-waku-2knv5dc9r-acidinfo.vercel.app/

[jinhojang6]

Adding node fetch-content.js breaks the build. You can see that Vercel is not working after adding this commit
cbf167d

The original source content <4 minutes should be changed to <4` minutes:
https://github.com/waku-org/research/blob/master/docs/rln-key-benchmarks.md#rln-tree-sync

PR to fix this: logos-messaging/research#117

[fryorcraken]

@jinhojang6 some of the CI checks did fail, is that ok?

[jinhojang6]

@fryorcraken Thanks for bringing this up.
The CI is working well locally and our Jenkins: https://ci.infra.status.im/job/website/job/docs.waku.org/

There was an issue in Vercel affecting only the deploy-master branch. The master branch is fine, and the page that raised the error before was published successfully: https://docs.waku.org/research/research-and-studies/rln-key-benchmarks

It seems that deploy-master is not working in Vercel but works fine in our Jenkins setup. I’ll double-check with the infra team, but I think we can safely ignore any CI issues from Vercel