Tezt: update records

What

This MR updates Tezt records from the last scheduled pipeline: https://gitlab.com/tezos/tezos/-/pipelines/1165754048

Why

For before_merging pipelines, the CI fetches Tezt records from the last successful scheduled pipeline. Those records are used for auto-balancing. If records cannot be fetched, the CI falls back on the records that are committed in tezt/records. Updating records in tezt/records from time to time ensures that we have a reasonable fallback.

In particular, currently, the last successful scheduled pipeline dates from too long ago; its artifacts have already expired. We made the artifact retention longer, but this will only start to kick in once a scheduled pipeline succeeds, and currently, scheduled pipelines fail because of multiple reasons (see https://gitlab.com/tezos/tezos/-/pipelines/1165754048). It is likely that this will not be resolved for a few days. So in the meantime, this MR ensures that we have a more up-to-date fallback.

How / Manually testing the MR

I just ran:

dune exec scripts/ci/update_records/update.exe -- --from 1165754048 --info

and committed the result.

I tagged this MR with ci--run-all-tezts and triggered pipeline https://gitlab.com/tezos/tezos/-/pipelines/1166265596 to be able to see if balancing is reasonable. Worst job seems to be https://gitlab.com/tezos/tezos/-/jobs/6106615696, which took 9min; fastest job seems to be https://gitlab.com/tezos/tezos/-/jobs/6106616123, which took 5min. The gradient between the 60 jobs is rather clean though. It seems on par with what we had in the past.

Checklist

• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR