Fix unforged L1UserTxs query in forgeBatch

Previously the code was only querying the unforged L1UserTxs of a particular
queue, but this was incorrect because there are always two non-forged queues:
the frozen one and the open one.

Replace it by a query to all the unforged L1UserTxs via a new HistoryDB method.

fix forge address balance printing removing the int64 casting

Avoid SQL error when checking value of token without usd on tx insert

Update L1CoordinatorTxFromBytes parser to EIP712

check the forge address balance before starting the node

Update AccCreationAuth signature hash to EIP-712

Compatible with `hermeznetwork/contracts` commit: `67726208723a40f2251953aaabf4d2b6221f8b13`
Compatible with `hermeznetwork/commonjs` commit: `dee266fb036a64bebc65756ebd5f0361929c110d`

Set the intermediary signal when exit TX is not inserted

Add forge delay to api get state

Update synchronizer.Sync2 to Sync from legacy impl

Reorg l2db before starting pipeline

Set gin debug mode via config

Calculate ForgeBatch gasLimit with parametrized formula

Fix missing timer reset in TxManager

Add API metric for time to forge L1 tx

Fix ZKI Exit Balance2 accumulate Amounts

Add new config setting `Debug.GinDebugMode`.  When set to true, gin will run in
debug mode.  If not set, gin will run in release mode.  Before this change, gin
always ran in debug mode, so to keep the same behaviour as before, set this
parameter to true

Add the following config parameters at
`Coordinator.EthClient.ForgeBatchGasCost`:
- `Fixed`
- `L1UserTx`
- `L1CoordTx`
- `L2Tx`
Which are the costs associated to a ForgeBatch transaction, split
into different parts to be used in the formula to compute the gasLimit.

Also, replace usage of time.Duration by time.NewTimer, because the later allows
replacing timers by stopping them before so that we never leak resources.

In http servers, first listen, then serve

Wait for serverProof before starting batch

Change how TX per Batch is calculated in state API endpoint

Diferentiate SQL connections by read write

Update ZKI generation to match circuit behaviour for Exit Amount>Balance

Currently the circuit does not use an Exit Leaf at the Exit MerkleTree
when the Amount=0 & EffectiveAmount=0, but it does use an Exit Leaf when
the Amount>0 but EffectiveAmount=0 (for example when tx.Amount >
sender.Balance). This is a particularity of the approach of the circuit,
the idea will be in the future to update the circuit and when Amount>0
but EffectiveAmount=0, to not add the Exit in the Exits MerkleTree, but
for the moment the Go code is adapted to the circuit and when an Exit
with Amount>0 & EffectiveAmount=0, it will be added to the Leaf of the
Exit MerkleTree.

- In test, doing the `net.Listen` outside of the goroutine guarantees that we
  are listening, so we avoid a possible datarace consisting of doing an http
  request before listening.
- In packages that run an http server: doing the listen first allows
    - Checking for errors when opening the address for listening before
      starting the goroutine, so that if there's an error on listen we can
      terminate grafecully
    - Logging that we are listening when we are really listening, and not
      before.

Add Prometheus initial setup

In API recommended fee, use minFeeUSD as min value

fix possible runtime error

node: remove redundant error check

tx manager: remove redundant error check

Stop using stateDB in API