CI: Tweaks to results.json

[IanButterworth]

• Stop attributing testset duration to tests from that testset, it doesn't make sense.
• Make the test name resemble (as far as possible) the original test call. Making the name independent of test outcome should make it easier to group tests and identify flaky ones.
• store repeat counts as tags, rather than in the name
• moves the save to inside the test workers, where all test info is available, and the save can be done in parallel to save time
• Includes Test: add option to record passes and enable it for CI #57690 for testing purposes

Todo:

• Determine if overhead is acceptable
• Remove timing prints
• Decide whether to merge this with Test: add option to record passes and enable it for CI #57690 or do that separately
• Figure out why the weakref test is failing. I think the Pass object might be retaining a reference?
  Identified: If a test like @test x == y passes, the Pass object retains x. I changed the weakref test to not do this by testing the outer function, as I don't think it's what that test is actually testing. But the question remains about whether this is unexpected behavior. Might alone be grounds for more eagerly streaming results to file so we can free the referenced values.
• add stdlib etc prefix to path to make repo links work
• consolidate/compress the jsons before uploading as a artifacts (250 artifacts is too many artifacts)

[vchuravy]

Stop attributing testset duration to tests from that testset, it doesn't make sense.

Can you expand on this a little bit?

[IanButterworth]

Currently we report that a test takes the duration of its parent testset. So @test x == 1 could be reported to take like 10 minutes. I think it's misleading.

[vchuravy]

Oh yeah, that's silly. Can we capture useful duration times?

[IanButterworth]

Our Result types don't currently store timing information. We could add it, but tbh I'm not sure it's any more useful. The useful information is somewhere inbetween the testset and the @test duration. If testsets were strictly a single test setup + test then it'd probably be fair to report testset duration. But testsets are very commonly a group of many sequential setups and tests.