Fix Issue #2805 - Resolve Patched False Negatives

[MaxwellOldshein]

This PR corrects the false positive issue for the Patched site as stated in: #2805.

From what I can gather, it appears that the URL for the Patched website has changed from https://patched.sh/ to https://patched.to/ due to the fact that traffic sent to the first URL is now currently set to redirect to the second URL automatically.

Originally, this site was leveraging the less accurate error_message detection method, but it appears as though the status_code methodology can be leveraged to more accurately detect whether or not usernames exist on the site:

Known Valid Username Behavior --> blue:

curl -Ls -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://patched.to/User/blue'                    

# 200 https://patched.to/User/blue

Known Invalid Username Behavior --> thisisatotallyfakeusername1234:

curl -Ls -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://patched.to/User/thisisatotallyfakeusername1234'                    

# 404 https://patched.to/User/thisisatotallyfakeusername1234

Username Behavior From Issue --> bapack.newbie:

curl -Ls -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://patched.to/User/bapack.newbie'           

# 404 https://patched.to/User/bapack.newbie

Closes #2805.

[github-actions]

Automatic validation of changes

Target	F+ Check	F- Check
Patched	✔️   Pass	❌   Fail

---

Failures were detected on at least one updated target. Commits containing accuracy failures will often not be merged (unless a rationale is provided, such as false negatives due to regional differences).

[github-actions]

Automatic validation of changes

Target	F+ Check	F- Check
Patched	✔️   Pass	❌   Fail

---

Failures were detected on at least one updated target. Commits containing accuracy failures will often not be merged (unless a rationale is provided, such as false negatives due to regional differences).