Update to docusaurus v3

[DhairyaMajmudar]

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Website is now building (tested by using command yarn build)

Fixes #602

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  This PR update the docusaurus from V2 to V3.7

• What is the current behavior? (You can also link to an open issue here)
  Currently, the website is running on docusaurus version 2

• What is the new behavior (if this is a feature change)?
  This PR aims to update docusaurus to its latest major release docusaurus version 3.7

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  Yes, it updates the docusaurus version 2 to its latest major version 3.7

• Other information:

For migration for docusaurus from V2 to V3 I have to make following syntax changes to the docs....

1. Changing <= to ≤
2. adding backticks to variables wrapped in brackets, Since without doing so the compiler was considering them as undefined variables and further failing the build

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign dingyin after the PR has been reviewed.
You can assign the PR to them by writing /assign @dingyin in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubeedge-bot]

Welcome @DhairyaMajmudar! It looks like this is your first PR to kubeedge/website 🎉

[DhairyaMajmudar]

/hold

[DhairyaMajmudar]

/unhold