ZKsync: provide public actions for fetching token addresses on L1 and L2 chains

[danijelTxFusion]

To enable seamless bridging of assets across chains, it is necessary to retrieve the corresponding token address on the other chain for a given asset. This involves implementing two public actions to facilitate the mapping between L1 and L2 token addresses.

Implementend the following public actions:

• getL1TokensAddress() - returns the L1 token address equivalent for a L2 token address.
• getL2TokensAddress() - returns the L2 token address equivalent for a L1 token address.

---

PR-Codex overview

This PR focuses on adding two public actions, getL1TokenAddress and getL2TokenAddress, to the ZKsync extension, enhancing the functionality for retrieving token addresses between L1 and L2.

Detailed summary

• Added getL1TokenAddress action to ZKsync extension.
• Added getL2TokenAddress action to ZKsync extension.
• Updated sidebar with links for getL1TokenAddress and getL2TokenAddress.
• Documented usage and parameters for both new actions.
• Implemented corresponding functions in src/zksync/actions.
• Added tests for both actions in getL1TokenAddress.test.ts and getL2TokenAddress.test.ts.
• Defined l2SharedBridgeAbi in src/zksync/constants/abis.ts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

🦋 Changeset detected

Latest commit: 7f0825d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
viem	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@danijelTxFusion is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
viem	✅ Ready (Inspect)	Visit Preview	Dec 5, 2024 6:39am