research: Figure out which functionality of zksync-cli is covered by foundry

[popzxc]

trafficstars

Component

Other (please describe)

Describe the feature you would like

Right now, we have zksync-cli as a "builder's swiss knife" tool. However, it feels like a lot of its functionality is covered by forge/cast already, e.g.:

• zksync-cli create is covered by forge init (it also supports templates)
• zksync-cli contract is covered by cast
• zksync-cli transaction info is covered by cast receipt
• zksync-cli wallet is covered by cast, though probably slightly less convenient
• zksync-cli bridge is not covered. But I guess we can add it to the our fork of cast, right?
• Starting in-memory node is covered by anvil-zksync. Starting dockerized setup will probably be covered once anvil-zksync supports L1.
• Starting explorer/portal is covered by zkstack CLI and it naturally feels better there.

The scope for this task is to analyze the functionality of zksync-cli and check whether it can be achieved by using forge/cast (or whether it naturally belongs to another scope like zkstack CLI). The outcome should be a comment in this issue.

Additional context

No response