[Android] Enable crash reporting by default on Nightly/Beta

[AlexeyBarabash]

Resolves brave/brave-browser#19857

This PR enables crash reporting by default on Nightly/Beta for new installations.

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one SECURITY REVIEW IS REQUIRED, PENDING
  https://github.com/brave/security/issues/860
• 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:

I. Nightly/Beta, fresh installation

1. Install Nightly/Beta browser as a fresh install
2. Go to Settings => Brave Shields & privacy
3. Ensure Automatically send diagnostic reports is turned on

II. Nightly/Beta, update installation

1. Open Nightly/Beta browser
2. At Settings => Brave Shields & privacy uncheck Automatically send diagnostic reports
3. Install Nightly/Beta browser as an update install
4. Go to Settings => Brave Shields & privacy
5. Ensure Automatically send diagnostic reports is still turned off

III. Stable, fresh installation

1. Install Stable browser as a fresh install
2. Go to Settings => Brave Shields & privacy
3. Ensure Automatically send diagnostic reports is turned off

IV. Stable, fresh installation

• similar to III. Stable, fresh installation

Note: Beta and Stable are not available yet, but it is possible to test that with own master-based builds.

[samartnik]

lgtm

[SergeyZhukovsky]

++

[deeppandya]

lgtm

[wchen342]

lgtm:+1:

[AlexeyBarabash]

Closing this, as onboarding PR #13405 handles this.