Handle "Allow in private" for Crypto Wallet and Greaselion

[darkdh]

Resolves brave/brave-browser#13279
Resolves brave/brave-browser#13506

This PR

1. Reinstall crypto wallet as non component extension while still leverage component updater's update mechanism
2. Add "not_allowed" to manifest of Greaselion
   (https://developer.chrome.com/docs/extensions/mv2/manifest/incognito/#not_allowed)

Submitter Checklist:

• There is a ticket for my issue.
• Used Github auto-closing keywords in the commit message.
• 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).
• Requested a security/privacy review as needed.

Reviewer Checklist:

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

Crypto Wallet

1. Launch Brave without --show-component-extenstion-options
2. Open brave://wallet and install wallet
3. Go to brave://extensions and go to details for Crypto Wallet extension
4. Allow in private option is available and disabled by default

Crypto Wallet: dApp

1. Launch Brave without --show-component-extenstion-options
2. Open brave://wallet and install wallet
3. Open https://www.cryptokitties.co/ in regular window and setup
4. The page should display
5. Open https://www.cryptokitties.co/ in private window
6. The page should show
7. Open brave://extensions/?id=odbfpeeihdkbihmopkbjmoonfanlbfcl and toggle on "Allow in private"
8. Open https://www.cryptokitties.co/ in private window again
9. We should be able to see locked wallet waiting to be unlocked

Crypto Wallet: Migration

1. Launch with older Brave
2. Open brave://wallet and install wallet
3. Go to https://goerli-faucet.slock.it/ and request 0.05 ETH
4. Make sure the balance shows 0.05ETH on goerli test network
5. Exit and Launch newer Brave with the profile
6. Open brave://wallet
7. It should still show 0.05 ETH

Greaselion

1. Launch Brave with --show-component-extenstion-options
2. Open brave://extensions and go to details for any greaselion
3. There is no Allow in private option because it is off by default and can not be toggled on

[bbondy]

Looks great, thanks! Please just make sure that existing data is preserved before merging.

[bbondy]

@srirambv @ryanml can you both test this to ensure no data loss for an existing profile before it is merged?

[darkdh]

verified migrate from component extension to normal extension, the ETH from faucet on testnet is still there

[ryanml]

++ looks good to me, confirmed no data loss

[srirambv]

Verification passed on

Brave	1.20.76 Chromium: 88.0.4324.79 (Official Build) nightly (64-bit)
Revision	bd1e9353659b2491dac971226a973ca3b5684a14-refs/branch-heads/4324@{#1520}
OS	Linux

• Verified no data loss on wallet after upgrade from 1.20.74
• Verified Allow in private is disabled by default
• Verified enabling it allows the extension to run in Private/Tor windows

Private	Tor

[srirambv]

This PR should also try to fix brave/brave-browser#13535