chore(prowlarr): Remove FlareSolverr warning

[csandman]

Pull Request

Purpose

I saw the warning about FlareSolverr being non-functional, but after checking the issue linked in the message (FlareSolverr/FlareSolverr#1253), it appears that it has been fixed. Also, after testing myself I can confirm that FlareSolverr is now working as expected. So, I figure that this warning is now misleading, and should be removed so people don't automatically give up on FlareSolverr as a potential solution.

Sorry if I didn't set this PR up correctly, I can adjust it if that's preferred.

Requirements

• These changes meet the standards for contributing.
• I have read the code of conduct.

Summary by Sourcery

Documentation:

• Remove the obsolete notice claiming FlareSolverr is currently non-functional from the Prowlarr FlareSolverr setup guide.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the Prowlarr FlareSolverr setup documentation by removing an outdated bug warning that stated FlareSolverr was non-functional and unlikely to be fixed, reflecting that the issue has been resolved and the tool is working again.

File-Level Changes

Change	Details	Files
Remove outdated FlareSolverr non-functional warning from the Prowlarr documentation.	Delete the admonition block that claimed FlareSolverr is currently non-functional and unlikely to be fixed Remove the embedded guidance directing users away from FlareSolverr and to a specific GitHub issue for status updates	docs/Prowlarr/prowlarr-setup-flaresolverr.md

Possibly linked issues

• #[Bug]FlareSolverr warning is out of date: PR updates the Prowlarr guide by deleting the outdated FlareSolverr non-functional warning described in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `docs/Prowlarr/prowlarr-setup-flaresolverr.md:13` </location>
<code_context>
-
 ## Install FlareSolverr

 Please follow the installation instruction from [FlareSolverr](https://github.com/FlareSolverr/FlareSolverr#installation){:target="\_blank" rel="noopener noreferrer"}
</code_context>

<issue_to_address>
**issue (typo):** Use 'instructions' instead of 'instruction' for correct grammar.

This aligns with referring to a set of steps from FlareSolverr.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Use 'instructions' instead of 'instruction' for correct grammar.

This aligns with referring to a set of steps from FlareSolverr.

[github-actions]

Deploying with ⚡ Cloudflare Pages

Latest commit:	543a41360ed62c4c46bfcbff599d1be7782e13bf
Status:	✅  Deploy successful!
Preview URL:	https://4b52a27b.trash-guides-6xu.pages.dev
Branch Preview URL:	https://pr-2599.trash-guides-6xu.pages.dev

[TRaSH-]

Removing it isn't the correct way because Cloudflare has been known to actively break tools like this, so your luck may vary.

So let me come up with a better suggestion in a few minutes

@csandman I added a few suggestions you can include in the PR. Once that's done, I'm willing to review and approve it.
If you don't respond within a week, I will close this PR, like all other single-effort abandoned PRs related to flaresolverr.

Just add all three suggestions to a batch using "Add suggestion to batch," and then you can merge all three at once