feat: support event nonce ctor input for deployments

[byte-bandit]

Related Github tickets

• Pigeon: support ctor input for batch_id VolumeFi/paloma#1002

Background

Adds support for setting the last observed event nonce from compass from within the constructor input during smart compass uploading. This allows updating the deployed compass contract without losing the current nonce value.

Testing completed

• test coverage exists or has been added/updated
• tested in a private testnet

Breaking changes

• I have checked my code for breaking changes
• If there are breaking changes, there is a supporting migration.

[byte-bandit]

This change does not require a new version of compass to be deployed. However, ONCE we re-deploy compass in the future, it will have to have support for this built in.

[taariq]

LGTM.

[taariq]

This change does not require a new version of compass to be deployed. However, ONCE we re-deploy compass in the future, it will have to have support for this built in.

@webelf101 do we need to make a PR for a new compass with this support so we can vote and redeploy compass next week?

[byte-bandit]

@taariq No need to redeploy compass next week just for the sake of supporting this change. Should be all good. Though next time we do upgrade compass for whatever reason, it will need to support this.

[taariq]

Thanks @byte-bandit, but my memory is short and I think we'll forget. Let's keep the upgrades moving. @verabehr let's open up tickets for upgrading compass to support this feature and then do the vote so we don't leave this dependent on organizational memory.

[verabehr]

I'm happy to open the ticket. I'm a bit confused what the actual change needed is though as @wc117 provided the correct ABI and said that no code change was needed for it. If this ABI is what is needed then what change is still pending?