Wrong interval when orchestrator queries for data commitment

[rach-id]

After bumping the version of Celestia, we started having the following log in orchestrator:

core0-orch    | I[2023-08-09|10:37:07.366] processing nonce                             nonce=3
core0-orch    | I[2023-08-09|10:37:07.372] signed Valset                                nonce=3
core0-orch    | I[2023-08-09|10:37:07.372] processing nonce                             nonce=2
core0-orch    | I[2023-08-09|10:37:07.380] signed Valset                                nonce=2
core0-orch    | I[2023-08-09|10:37:07.380] processing nonce                             nonce=1
core0-orch    | I[2023-08-09|10:37:07.385] signed Valset                                nonce=1
core0-orch    | I[2023-08-09|10:37:10.847] enqueueing new attestation nonce             nonce=4
core0-orch    | I[2023-08-09|10:37:10.847] processing nonce                             nonce=4
core0-orch    | E[2023-08-09|10:37:10.849] failed to process nonce, retrying            nonce=4 err="error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). RPC error -32603 - Internal error: last block 102 is higher than current chain height 101"
core0-orch    | I[2023-08-09|10:37:10.849] trying to recover from error...              
core0-orch    | I[2023-08-09|10:38:06.680] enqueueing new attestation nonce             nonce=5
core0-orch    | I[2023-08-09|10:38:10.850] retrying                                     retry_number=0 retries_left=6
core0-orch    | I[2023-08-09|10:38:10.862] signed commitment                            nonce=4 begin_block=1 end_block=102 data_root_tuple_root=0x8ab1f80ee0a89c54f27d57d4638ac200944da6bb2a4447de55577726d54a1913
core0-orch    | I[2023-08-09|10:38:10.862] succeeded                                    retries_number=0
core0-orch    | I[2023-08-09|10:38:10.862] processing nonce                             nonce=5
core0-orch    | I[2023-08-09|10:38:10.877] signed commitment                            nonce=5 begin_block=102 end_block=203 data_root_tuple_root=0x0aa87f2b4564bc2f06c8084ea5333332c37597c828186d018b2893e0ed276140
core0-orch    | I[2023-08-09|10:39:06.746] enqueueing new attestation nonce             nonce=6
core0-orch    | I[2023-08-09|10:39:06.747] processing nonce                             nonce=6
core0-orch    | I[2023-08-09|10:39:06.758] signed commitment                            nonce=6 begin_

This is due probably to mismatching ranges. We need to fix this