updateL1FromL1
  ⚪ Updates are accepted
  ⚪ Future +1 updates are  not accepted
  ⚪ Future -1,0,1 updates are  not accepted
  ⚪ Add twice the same deposit with requestId
  ⚪ Add twice the same request id but different deposits
  ⚪ Add twice the same request groups
  ⚪ Old Ids can be included but wont be considered
  ⚪ Old Ids can be included on some other update and wont be considered
  ⚪ An update with no new updates will fail
  ⚪ An update with a gap will fail
  ⚪ An update that is not ordered will fail
  ⚪ An update with two identical deposits must be executed correctly
  ⚪ Every update item is validated
updateL1FromL1 - errors › Update with gap: true
  ⚪ An update including gap? : true at positions 0
  ⚪ An update including gap? : true at positions 1
  ⚪ An update including gap? : true at positions 2
  ⚪ An update including gap? : true at positions 3
updateL1FromL1 - errors › Update with gap: false
  ⚪ An update including gap? : false at positions 0
  ⚪ An update including gap? : false at positions 1
  ⚪ An update including gap? : false at positions 2
  ⚪ An update including gap? : false at positions 3
updateL2FromL1 - cancelResolution and deposit errors
  ❌ When a cancel resolution fail, maintenance mode will be triggered automatically
	Error: Max blocks reached without getting read rights
  ❌ [BUG] When a cancel resolution fail, the whole update wont be stored
	Error: Max blocks reached without getting read rights
  ❌ When we have a failed deposit and send it again, it will result in no-execution again
	Error: Max blocks reached without getting read rights
  ❌ GIVEN two deposit with u128max-1 amount THEN second deposit fails
	Error: Max blocks reached without getting read rights