feat: remove local db from aggsender

[goran-ethernal]

Description

This PR removes the local aggsender db, and uses in memory saving of the last sent certificate.

On startup, the aggsender will get the last sent certificate for its network by using the interop_getLatestKnownCertificateHeader rpc endpoint on agglayer. If it is nil, it means that agglayer doesn't have any certificates from our network. If it has, we will save it in memory as the last sent certificate.

Then, the flow is as it was:

• we wait for the moment in the L1 epoch to build a new certificate.
• if the last sent certificate is nil (agglayer has no certificates from our network), or if it's status is Settled or InError, aggsender will proceed to build a new certificate.
• if the last sent certificate has any other status than Settled or InError it means we can not build a new certificate, so we wait for the next chance to build it.

Pros of removing local aggsender db:

• we are relaying solely on agglayer as a source of truth.
• code is less complex.
• aggsender config is smaller.
• aggsender is faster since it saves the last sent certificate in memory, and it doesn't need to query db.

Cons:

• No history tracking.
• Some situations in production can be more difficult to track. e.g: there are 2 aggsenders sending certs with same NetworkID, or someone was manually sending certificates to the agglayer.

[vcastellm]

Rebase to deduce diff?

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud