Description

Per #531 its unexpected that randomly generated values in different tests would be identical. It's common in test suites to use randomly generated identifiers to help maintain test isolation and provide easier-to-understand logs.

Examples:

• one may be using a third party system that cannot be reset but where isolation can be provided by using new unique identifiers for each test.
• one may be using unique s3 buckets per test (and want them to persist for review afterwords)
• one may be reading test suite logs and want to find logs with a specific identifier related to a specific test failure

One could use --randomly-dont-reset-seed but then they would lose the reproducibility and repeatability.

I propose that the node_id of the test (and the test run seed) be used to deterministically generate a unique seed for that test (instead of all tests being reset to the same fixed value).