protocol contract deployment verification via CI

[Ashar2shahid]

Closes #1594

This add CI Verification to the protocol contracts using the verify-local script. I opted to return the list of all failed verifications and then throw the error instead of throwing an error at the first failed verification.

• I created a separate workflow file for deployment-verification due to the path filter only being applicable on a per workflow basis, this means that if we want to run the CI only if the airnode-protocol folder changes then we need a separate workflow.
• we can use the paths-filer action if we want to do the deployment-verification and check if the airnode-protocol folder has changed in the Continuous Build workflow but its a third-party.
• we can opt out of checking if the airnode-protocol folder has changed and run the CI on every workflow-run by incorporating it as an extra step of the Continuous Build workflow

[Ashar2shahid]

As seen here: https://github.com/api3dao/airnode/actions/runs/4041541899/jobs/6948239143 the CI is failing because of :

• some chains not existing (roptsen,rinkeby,kovan)
• going down frequently (gnosis-testnet)
• the RPCs being faulty (polygon)

[bbenligiray]

I took a brief look, I can review again after #1562 is merged

Just remove the ropsten, rinkeby, kovan deployments. It should have been done as a part of #1280 While at it, remove gnosis-testnet and metis-testnet too. They can be added back in a separate PR to close #1628.

[bbenligiray]

It makes sense to move this under test:, but the single network local verification came in handy while doing the deployments

[Ashar2shahid]

cool I'll try to accommodate both

[Ashar2shahid]

use test:verify-local:network for single network verification

[bbenligiray]

Can you merge #1562 and merge master to 1594 so that we know that the CI also works for the new chains?

[Ashar2shahid]

Checks are passing, good to merge

[bbenligiray]

I think the implementation in verify-local.ts could be better compartmentalized to be more reusable. The current thing addresses the issue though so maybe someone will come back to this later.