Add Ratios API for coingecko coin markets data

[nvonpentz]

Resolves brave/brave-browser#21455
Resolves brave/brave-browser#20674

This branch previously only included backend changes, but now includes both frontend and backend changes.

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

Market.Data.mov

[nvonpentz]

Waiting on @muliswilliam to validate this branch works with his frontend code + the new ratios endpoint before requesting review.

[diracdeltas]

this probably needs a privacy review - note this comment about coingecko: https://github.com/brave/security/issues/663#issuecomment-967770990

also i see this adds some JSON parsing - if it happens in the main process, ideally it would wait until @spylogsster's work on rust JSON validation is done and use that for compliance with rule of 2 https://chromium.googlesource.com/chromium/src/+/master/docs/security/rule-of-2.md

[bbondy]

Pls avoid dependencies at all costs, only add if absolutely necessary (and if adding, they need security review).

[diracdeltas]

Pls avoid dependencies at all costs, only add if absolutely necessary (and if adding, they need security review).

I mentioned this in the previous PR for the front-end part of this, but I feel this feature should be displayed in a chrome-untrusted frame given the added deps. cc @petemill

[yrliou]

backend change LGTM.

[muliswilliam]

@diracdeltas @bbondy I have removed any dependencies I had introduced to this feature. Does it still need to be in chrome-untrusted frame?

[diracdeltas]

I have removed any dependencies I had introduced to this feature. Does it still need to be in chrome-untrusted frame?

i still see some new deps in https://github.com/brave/brave-core/pull/12510/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519 - are those not used in the webui?

regardless i feel this is a good candidate for chrome-untrusted sandboxing because it's displaying external untrusted data

[muliswilliam]

I have removed any dependencies I had introduced to this feature. Does it still need to be in chrome-untrusted frame?

i still see some new deps in https://github.com/brave/brave-core/pull/12510/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519 - are those not used in the webui?

regardless i feel this is a good candidate for chrome-untrusted sandboxing because it's displaying external untrusted data

The @solana/web3.js dependency is already on master. Most likely added to add solana support. Aren't most interfaces on the wallet displaying external data? For example asset price history is fetched from coingecko too. As far as I know, it is not sandboxed.

All changes implemented

[goodov]

chromium_src changes lgtm.