Local state pref to use from Java

[AlexeyBarabash]

Resolves brave/brave-browser#27632

Intruduced BraveLocalState class.

Removed methods from BravePrefServiceBridge which were used to access these local_state prefs:

• BravePref.P3A_ENABLED
• BravePref.P3A_NOTICE_ACKNOWLEDGED
• BravePref.STATS_REPORTING_ENABLED
• BravePref.SAFETYNET_STATUS
• BravePref.ENS_RESOLVE_METHOD
• BravePref.SNS_RESOLVE_METHOD
• BravePref.UNSTOPPABLE_DOMAINS_RESOLVE_METHOD
• BravePref.ENS_OFFCHAIN_RESOLVE_METHOD

Removed unused Java/JNI methods:

• BravePrefServiceBridge.setReferralAndroidFirstRunTimestamp;
• BravePrefServiceBridge.setReferralCheckedForPromoCodeFile;
• BravePrefServiceBridge.setReferralInitialization;
• BravePrefServiceBridge.setReferralPromoCode;
• BravePrefServiceBridge.setReferralDownloadId.

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

New features are not added with this PR. The test plan is required to verify nothing is broken.

I. brave.p3a.enabled

1. Make fresh installation
2. Launch browser, on FTRW uncheck Share completely private and anonymous product insights about what features are being used by Brave's users.
3. Open brave://local-state, must exist

 "p3a": {
         "enabled": true,

entry.
4. Go to app menu => Settings => Brave Shields & privacy, Allow privacy-preserving product diagnostic (P3A) must be unchecked
5. Check Allow privacy-preserving product diagnostic (P3A) switch
6. Open brave://local-state, the entry should look

 "p3a": {
         "enabled": false,

II. brave.stats.reporting_enabled

1. Open app menu => Settings => Brave Shields & privacy, turn off Automatically send daily usage pings
2. Open brave://local-state, find reporting_enabled should be false
3. Open again app menu => Settings => Brave Shields & privacy, Automatically send daily usage pings must be unchecked

III. safetynet.status
According to the code, the Brave Rewards grant should be retreived successfullt to verify it works as before.

IV. brave.unstoppable_domains.resolve_method

1. Open app menu => Settings => Brave Shields & privacy => Unstoppable Domains, switch it to Enabled
2. Open brave://local-state, find resolve_method near unstoppable_domains, it should be

"unstoppable_domains": {
         "resolve_method": 3
      },

3. Relaunch browser, open app menu => Settings => Brave Shields & privacy => Unstoppable Domains, it should still be Enabled

V. brave.ens.resolve_method

1. Open app menu => Settings => Brave Shields & privacy => Ethereum Name Service, switch to Enabled
2. Open brave://local-state, find resolve_method near ens, it should be

"ens": {
         "resolve_method": 3
      },

3. Relaunch browser, open app menu => Settings => Brave Shields & privacy => Ethereum Name Service, it should still be Enabled

VI. brave.sns.resolve_method

1. Open brave://flags => Enable Solana Name Service support => Enabled, relaunch browser
2. Open app menu => Settings => Brave Shields & privacy => Solana Name Service, switch to Enabled
3. Open brave://local-state, find resolve_method near sns, it should be

"sns": {
         "resolve_method": 3
      },

4. Relaunch browser, open app menu => Settings => Brave Shields & privacy => Solana Name Service, it should still be Enabled

VII. brave.ens.offchain_resolve_method

1. Open app menu => Settings => Brave Shields & privacy => Unstoppable Domains, switch ENS offchain lookup to Enabled
2. Open brave://local-state, find resolve_method near unstoppable_domains, it should be

"ens": {
         "offchain_resolve_method": 2,

3. Relaunch browser, open app menu => Settings => Brave Shields & privacy => Unstoppable Domains, ENS offchain lookup should still be Enabled

[SergeyZhukovsky]

++

[bridiver]

You should not do this, the actual writing of prefs to disk should be left to the pref service