[Snyk] Fix for 1 vulnerabilities

[RealTschoegl]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• docs/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-MINIMATCH-15353389	828

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Note

Upgrade docs build tooling to address a Snyk vulnerability by moving webpack to 5.1.1 and webpack-dev-server to 4.0.0

Update docs/package.json to use webpack 5.1.1, webpack-dev-server 4.0.0, copy-webpack-plugin 7.0.0, and codesandboxer 0.5.0 in the docs build pipeline.

📍Where to Start

Start with the dependency updates in package.json.

^{Macroscope summarized 9021929.}

[macroscopeapp]

This is a straightforward Snyk security fix that updates dev dependencies in the docs/package.json file. The changes don't affect the main library's runtime behavior - they only update build tooling for documentation. As an admin making a standard security update, this is safe to approve.