feat(tokens) add CAD, FED and JPY tokens

[hmoragrega]

Fixes:
https://injective-labs.atlassian.net/browse/HELIX-604
https://injective-labs.atlassian.net/browse/HELIX-576
https://injective-labs.atlassian.net/browse/HELIX-497

I used the values from the latest injective lists
@ThomasRalee are we sure these denom values are correct?

[coderabbitai]

Warning

Walkthrough skipped

File diffs could not be summarized.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5982ab1 and 4d32bf3.

Files selected for processing (1)

• pkg/token/token_meta.json (1 hunks)

Files not summarized due to errors (1)

• pkg/token/token_meta.json: Error: Server error. Please try again later.

Additional comments not posted (2)

pkg/token/token_meta.json (2)

1921-1931: Addition of JPY Token Metadata

The addition of the JPY token metadata looks correct. The structure follows the existing pattern, and the logo URL is correctly formatted. Please ensure the denom value "jpy" is confirmed by the relevant financial authority or conforms to internal standards.

---

1933-1943: Addition of CAD Token Metadata

The CAD token metadata has been added correctly. The format is consistent with other entries, and the logo URL is properly included. Please verify the denom value "cad" as per the financial standards or internal guidelines.

[ThomasRalee]

We should only add base & quote denoms of spot market on this list.