(Wallet) Load Meld icons correctly in Buy WebUI

[simoarpe]

Resolves brave/brave-browser#44321

In android_wallet_page_ui.cc registers sanitized image source data source to serve chrome://image URLs.

android_wallet_page_ui.cc contains Android-specific implementation and should follow the same approach of wallet_page_ui.cc for registering the required data sources.
SanitizedImageSource is in charge of providing the source of chrome://image that is referenced by chrome::kChromeUIImageHost constant.

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

• Create a Wallet
• Navigate to Buy section
• Observe all the icons are loaded correctly

[Douglashdaniel]

++ Wallet Front-end

[diracdeltas]

do we still need data or chrome://erc-token-images in https://github.com/brave/brave-core/pull/27885/files#diff-0e0eb6acfeba674a0c6a698e22c04773ae563f8629ac3841fc1ec59b6d3e5b02R71 above?

[simoarpe]

@diracdeltas, I confirm both data: and chrome://erc-token-images are still needed for the Android Wallet.

data: is still required to load correctly brave://wallet/crypto/fund-wallet, without it TestMeldPageAppearing fails.
chrome://erc-token-images is still required to load correctly brave://wallet/crypto/deposit-funds, without it TestDepositPageAppearing fails.

[SergeyZhukovsky]

++