bug: Shard IDs is mixed-up leading to shard filenames to be incorrect

[khorolets]

Recently, we've been reported about the mixed-up Shard Id in the StreamerMessage structure and actual data under the specific key having a different shard_id value.

It means that we have something like:

...
"shards": {
  "shard_id": 0,
  "chunk": { "shard_id": 1, ... }
  ...
},
...
}

This bug originated from the NEAR Indexer Framework implementation and has been recently fixed near/nearcore#12579, but it still needs time to be included in the release. We will probably see it in the 2.5.x

However, on the Lake Indexer side, we naively rely on that piece and can fix it immediately.