(Wallet) Implement onboarding initial screen and TOC screen

[simoarpe]

Resolves brave/brave-browser#35713

Implements new initial onboarding screen and new terms of use screen.

Light Mode

Dark Mode

Figma design: https://www.figma.com/file/oXIiv45pIhF2RGlpEjOfUg/Wallet-onboarding?node-id=6223%3A70942&mode=dev

Main umbrella issue: brave/brave-browser#35294

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• 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/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

• Erase any wallet data, if any.
• Navigate to Wallet section
• Observe new onboarding creation screen.
• Tap on "Need a new Wallet".
• Observe new terms of use screen.
• Verify "continue" button is enabled only when both checkboxes are ticked
• Verify "Terms of use" clickable span points to https://brave.com/terms-of-use/

[github-actions]

[puLL-Merge] - brave/brave-core@21905

Description

This pull request introduces several enhancements and new features to the Brave wallet on the Android platform. It includes updates to the user interface and the addition of new resources for improving the wallet onboarding experience and functionality.

Changes

Changes

Resources Added

• Drawable Resources: New icons and other drawable resources for wallet onboarding, including new_wallet.xml, restore_wallet.xml, and icons for various cryptocurrencies like Coinbase, MetaMask, and Phantom.
• Language Strings: New strings for UI text, including titles and descriptions for new wallet setup and restoring an existing wallet, terms of use acknowledgment, and others.
• Styles: New styles for wallet-related UI components, especially for onboarding card views and buttons.

Java Source Files

• BraveWalletActivity.java: Significant changes for handling the wallet onboarding flow, including terms of use and options for setting up a new wallet or restoring an existing one.
• OnboardingInitWalletFragment.java: Updated to support animated backgrounds during onboarding and rearranged UI components with new cards for new wallet setup and wallet restore options.
• CryptoWalletOnboardingPagerAdapter.java: Refactored to support the addition of new onboarding steps dynamically.
• OnboardingTermsOfUseFragment.java: A new fragment to display terms of use during the onboarding process.

Security Hotspots

1. Dynamic Fragment Handling (CryptoWalletOnboardingPagerAdapter.java): Changes in how fragments are dynamically replaced or added during the onboarding process need careful review to ensure that fragment lifecycles are properly managed and that this dynamic behavior doesn't introduce any memory leaks or unexpected behaviors.

2. New Resource Files Handling: The introduction of several new drawable and layout resources, along with dynamically loaded content (e.g., animated backgrounds), should be reviewed to ensure efficient resource management and optimal performance on a wide range of devices.

3. User Input and External URLs: The handling of user input, especially in new onboarding forms and the "Terms of Use" with clickable links (OnboardingTermsOfUseFragment.java), should be reviewed for potential security implications, including but not limited to injection attacks or improper handling of external URLs.

4. Storage and Handling of Sensitive Information: Any changes related to how sensitive information, such as wallet recovery phrases or private keys, is stored or handled during the onboarding process necessitate a thorough security review to prevent data leakage or unauthorized access.

[mkarolin]

strings++

[SergeyZhukovsky]

++