bug: proxy: step WaitingGERInjection as result have the L1 block

[joanestebanr]

Bug Report

The block of WaitingGERInjection is the same as WaitingGERInjection. So can't be used to calculte timing and doesn't give any new data.
To get this info is calling to bridge service /bridge/v1/injected-l1-info-leaf this must provide more information

{
      "step_index": 1,
      "step_name": "WaitingGERInjection",
      "status": "done",
      "start_date": "2026-08-31T17:43:20.307055948+02:00",
      "end_date": "2026-08-31T17:44:05.091708378+02:00",
      "result": {
        "ger": "0x330d1f1546dc784aa465fdf83fb9d88e0a3778064d74e182c1dfb803ef155c16",
        "block_number": 11606405,
        "block_timestamp": 1788188124
      }
    },

(...)

{
      "step_index": 1,
      "step_name": "WaitingGERInjection",
      "status": "done",
      "start_date": "2026-08-31T17:43:20.307055948+02:00",
      "end_date": "2026-08-31T17:44:05.091708378+02:00",
      "result": {
        "ger": "0x330d1f1546dc784aa465fdf83fb9d88e0a3778064d74e182c1dfb803ef155c16",
        "block_number": 11606405,
        "block_timestamp": 1788188124
      }
    },

Proposed fix

• Add new fields to bridge_service end-point injected-l1-info-leaf:

  • injected_l2_block_num
  • injected_l2_block_timestamp
    These fields are optional (to keep compatibility)

• Modify result for WaitingGERInjection

      "result": {
        "L1InfoTreeLeaf": {
        "ger": "0x330d1f1546dc784aa465fdf83fb9d88e0a3778064d74e182c1dfb803ef155c16",
        "block_number": 11606405,
        "block_timestamp": 1788188124
       }, 
      "L2InjectedGER": {
        "block_number": xxx,
        "block_timestamp": yyy
      }
      }

L2InjectedGER is optional