Store ZKC and closing reason on batch table

[arnaubennassar]

This will help analize the behaviour of the network. Note that closing reason only applies to trusted sequencer and trusted state!!

[Psykepro]

Steps to implement:

• create migration file db/migrations/state/000x.sql which to add columns for each ZK Counter and the closing_reason and for closing reason to state.batch table
• storing batch constraints 2 possible solutions:
  • on closing batch we store ZK Counters used by all txs
  • on creating a batch initializing the column values with max ZK Counters and updating on each successful tx processed the values in the columns (this case will need also update to add back the ZK Counters for each L2 Block deleted to the batch in synchronizer on L2 REORG)
• on closing batch, we save the reason

[ToniRamirezM]

I would consider (we can debate):

• Use a jsonb column to store the whole ZKCounters struct
• I would go for the first approach: easier and more performant