Add l10n support of resolve method options in decentralized DNS settings

[yrliou]

Resolves brave/brave-browser#14862
Resolves brave/brave-browser#14864

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
• 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:

1. in brave/settings/extenstions, set resolve method of Unstoppable Domains to Ask, visit brave.crypto, should see interstitial page to opt-in.
2. Change settings to Disabled in settings, and refresh brave.crypto page, should see error page.
3. Change settings to DNS over HTTPS in settings, and refresh brave.crypto page, should now see page rendered normally.

[yrliou]

Apply skip-CI labels to retry on Android only which was the only platform failed.

[yrliou]

Android build was manually triggered without git cache with help from devops team and it was green, https://ci.brave.com/blue/organizations/jenkins/pr-brave-browser-resolve_method_l10n-android/detail/pr-brave-browser-resolve_method_l10n-android/15/pipeline, merging.