feat: add blacklisted drive go link

[elibosley]

Before Submitting This PR, Please Ensure You Have Completed The Following:

1. Are internal links to wiki documents using relative file links?
2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
5. Is the build succeeding?

Summary by CodeRabbit

• New Features
  • Introduced a URL redirect that seamlessly guides users from an outdated page to the current documentation on USB flash device storage management.

[coderabbitai]

Walkthrough

The pull request updates the documentation configuration by adding a new redirect mapping. The change directs users from the outdated URL /go/blacklisted-usb-flash-device to /unraid-os/manual/storage-management/#blacklisted-usb-flash-device within the Docusaurus configuration file. No alterations have been made to the existing control flow or redirect logic.

Changes

File	Change Summary
docusaurus.config.js	Added new redirect mapping: from /go/blacklisted-usb-flash-device to /unraid-os/manual/storage-management/#blacklisted-usb-flash-device.

Possibly related PRs

• feat: redirect for patch routes #247: The changes in the main PR, which add a new redirect mapping in docusaurus.config.js, are related to the modifications in the retrieved PR that also involve changes to the same file, specifically concerning redirect functionality.
• feat: generate go-links for releases #249: The changes in the main PR, which add a new redirect mapping in docusaurus.config.js, are related to the modifications in the retrieved PR that also involve the docusaurus.config.js file, specifically the reformatting of redirect configurations.

Poem

I'm a little rabbit with a coding beat,
Hopping through URLs to make paths neat.
Redirects now flourish in a neatly set lane,
Guiding users from old routes without any strain.
Celebrate the change, and let the new path lead—
A leap of faith in every line of code indeed!
🐰🌟 Happy coding!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between d4eb5dc and a633ea2.

📒 Files selected for processing (1)

• docusaurus.config.js (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docusaurus.config.js

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build
• GitHub Check: AWS Amplify Console Web Preview

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[aws-amplify-us-west-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-251.d1o5s833kbd339.amplifyapp.com