Redirects additional details button target URL on crashes page.

[mkarolin]

Fixes brave/brave-browser#10185

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. 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-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

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.

[bridiver]

I think we should redirect the url to brave-browser issues, but if are going to remove the button I think it can be hidden in css without patching cc @petemill

[petemill]

This is not a polymer page, so we need to patch in a crashes_overrides.js or a crashes_overrides.css include to the .html, and remove or hide the button through one of those.

[petemill]

I agree we can have this pre-fill an issue on github via query params similar to what it looks like chromium is doing
https://help.github.com/en/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters

But if you want to hide it in this PR and create a new issue for that functionality, I think that would be fine too cc @rebron

[rebron]

Either hide or redirect to github is fine. Thanks for the pointer @petemill

[mkarolin]

Updated PR with redirect instead of hide: @bridiver @petemill

[iefremov]

bugs_chromium_pattern

[kjozwiak]

Verification PASSED on macOS 10.15.5 x64 using the following build:

Brave | 1.12.18 Chromium: 83.0.4103.97 (Official Build) nightly (64-bit)
-- | --
Revision | 326d148b9655369b86498d9ecca39f63dd2bdd2d-refs/branch-heads/4103@{#657}
OS | macOS Version 10.15.5 (Build 19F101)

• ensured that both brave://crash and brave://gpucrash are appearing under brave://crashes
• ensured that clicking on Provide additional details opens GH and not
• ensured reports are being sent when Help improve Brave's features and performance is enabled via brave://settings/privacy

Created the following crashes and ensured they appeared in BackTrace

• 7e590000-1c55-8704-0000-000000000000
• 7d590000-1c55-8704-0000-000000000000
• 80590000-1c55-8704-0000-000000000000

As per the above, redirecting from bugs.chromium.org -> GH