[FUN-877] persist data fetched from allowlist contract

[agparadiso]

Description

This mr aims to persist data from the allowlist contract into the node's db in order to speed up the re-start of a node.

Changes implemented

Tos contract

• implementation of getAllowedSendersCount() and getAllowedSendersInRange to iterate in batches over the allowed senders
• implementation of getBlockedSendersCount() and getBlockedSendersInRange to iterate in batches over the blocked senders
• change the s_blockedSenders type to EnumerableSet.AddressSet to be able to iterate.

Gateway handler

• Small refactor in which allowlist and subscriptions have their own pkg
• ORM layer for allowlist that will persist the list of allowed senders in batches of a configurable size
• This ORM has a DeleteAllowedSenders method that will be invoked in order to delete from the functions_allowlist table every address that has been blocked onchain.
• Feature flag for this feature that will enable us to deploy this while still being backwards compatible with previous versions of the contract that do not includes the methods introduced here. If the feature is disabled, we are not storing the allowlist given that we would not be able to sync with the blocked list.

Outside of scope

We are not taking into account the methods necessary to migrate existing blocked senders. this will be taken into account in a separate pr

How was this tested

The feature has been covered by unit and integration tests + validated on DB by starting a local node.
Further testing on staging will be done after merging

[github-actions]

I see that you haven't updated any README files. Would it make sense to do so?

[github-actions]

Go solidity wrappers are out-of-date, regenerate them via the make wrappers-all command

[github-actions]

Go solidity wrappers are out-of-date, regenerate them via the make wrappers-all command

[cl-sonarqube-production]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

84.1% Coverage
0.0% Duplication