release-22.2: workload: use different random seeds by default

[renatolabs]

Backport 1/1 commits from #95326.

/cc @cockroachdb/release

---

This changes most of the workloads that take a --seed command line flag so that they use a different, randomly generated seed on each run. Previously, they would all default to 1, making every run of the workload produce the same data and operations. That behavior is good for reproducing a specific pattern or behavior, but workloads that have a random element should exploit that randomness by default.

When a workload is invoked, a random seed is generated and logged. Users are still able to specify their own seeds by passing the --seed flag.

Resolves #88566.

Release note (cli change): workloads that take a --seed argument
used to default to 1. Now, they use a randomly generated seed in
each run. Users can still pass a custom seed with the --seed flag.

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is