Feat: Construct a mechanism where the test run is guaranteed to be unique - avoid the possibility that unconnected runs are lumped together. #229
Description
In the TestRun we have a TestProjectName and a TestSeed. When a suite runs, it uses these two to signal which test run it is associated with. The TestSeed in the clients is typically a timestamp. If, in the same project, two tests runs were to start at the same time, they would be lumped together. This is very unlikely, but possible. So not a high priority, but something that should be handled
Construct a mechanism where the test run is guaranteed to be unique - this may require interacting with clients - a possible approach would be to call an API initially and have the fern-reporter issue a TestSeed.
Refusing to allow a TestSeed not issued by the Fern Reporter would also protect against a client accidentally reusing TestSeeds.