Test the CLI command

[bbenligiray]

Assuming that the CLI command was going to be very static, I've been just testing all conditions manually. We do appear to be adjusting it though, so automated tests would be nice. I would refer to airnode-admin e2e tests for how that could be done.

[hiletmis]

The CLI provides two commands:

• print-api3readerproxyv1-address
• compute-dapp-id

Testing compute-dapp-id
The compute-dapp-id command can be tested with deterministic inputs using an iteration. This makes it straightforward to validate expected outputs without external dependencies.

Testing print-api3readerproxyv1-address
This command depends on a real deployed proxy contract to return consistent results. For testing, there are two main approaches:

1. Mock
   Simulate the call:

   code = await provider.getCode(proxyAddress); 

2. Use a Real Proxy
   Provide a known deployed proxy address on a specific network for an integration-style test.

Which strategy should be followed?

[bbenligiray]

Actual RPC provider calls in an e2e test is acceptable but testing this will require a lot of calls if different aliases/chain IDs/dAPI names are tried. So I would go with mocking the call.