Remove YouTube and Instagram share ID parameters from URLs

[fmarier]

Fixes brave/brave-browser#34719 and brave/brave-browser#35094

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• 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 wiki
  • npm run lint, npm run presubmit wiki, 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/Query-String-Filter

Test Plan:

1. In a new browser profile with Shields set to normal adblocking (not aggressive).
2. Open the network tab of the devtools.
3. Paste https://www.youtube.com/watch?v=dQw4w9WgXcQ&si=YjziZuccJeIE-b6z in the URL bar.
4. Filter for just document requests and ensure that the 200 OK request (ignore the 200 Internal Redirect request) does not include the si parameter.
5. Delete the existing browser profile and create a new one.
6. Repeat the test with https://youtu.be/watch?v=dQw4w9WgXcQ&si=YjziZuccJeIE-b6z.
7. Repeat the test with https://www.instagram.com/p/C1nNxSbsAzk/?utm_source=ig_web_button_share_sheet&igsh=ZDNl...IxNw== confirming that the igsh parameter is only present in Internal Redirect requests.

Here's what it looks like before the change in this PR:

and here's the new expected result as of this PR:

The youtu.be URL will now show a 303 Internal Redirect instead of a 303 See Other:

Note: this test will only work the first time. You need to delete the profile or clear all data before testing this otherwise service workers will interfere with the requests.

[ryanbr]

Would it be safer to limit too www. ? would it need to apply to m.youtube.com, music.youtube.com, tv.youtube.com ?

[fmarier]

Would it be safer to limit too www. ? would it need to apply to m.youtube.com, music.youtube.com, tv.youtube.com ?

It automatically includes subdomains. I've added a comment to that effect in the PR.

[iefremov]

probably with std::array we can keep the whole thing constexpr

[fmarier]

I tried to do this, but I wasn't able to make it work as a constexpr with an std::array because the size of the array is variable.