Fix HTTPSE redirects having stronger precedence over adblock redirects

[antonok-edm]

Resolves brave/brave-browser#26415

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

Note the STR from the associated issue:

1. Add this as a custom filter:
   ||google-analytics.com/analytics.js$script,redirect=google-analytics.com/analytics.js [...]

2. go to http://markkystreams.com/ [...]

3. Open shields and it will say google-analytics.com/analytics.js was upgraded and blocked.

4. Open DevTools and you will see analytics is in the source list, so Shields information is not accurate since the script wasn't blocked, because if it was, it wouldn't be in the list and it wasn't redirected since the script is the same analytics script used by the page, not the uBlock one.

In step 3, verify that http://www.google-analytics.com/analytics.js appears in the counter menu next to the Block trackers and ads setting rather than the Upgrade connections to HTTPS setting.

In step 4, verify that the analytics.js entry in the network panel has contents (Response tab) starting with the uBlock Origin copyright header.

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.47.41 Chromium: 107.0.5304.91 (Official Build) nightly (64-bit)
-- | --
Revision | 3d5948960d62418160796d5831a4d2d7d6c90fa8-refs/branch-heads/5304@{#1097}
OS | Windows 11 Version 22H2 (Build 22621.755)

Reproduced the original issue using the STR/Case outlined via #15754 (comment) using 1.47.39 Chromium: 107.0.5304.91 as per the following:

Example	Example	Example

Using the same STR/Cases, verified that google-analytics.com/analytics.js wasn't appearing under Upgrade connections to HTTPS and ensured that analytics.js via the Response tab displayed the uBlock Origin header as per the following:

Example	Example	Example