Memoised resources test is flaky

This issue was copied over from: https://github.com/disneystreaming/weaver-test/issues/475
It was opened by: keynmol

Not sure if it pops up more often because we're going through more SS updates or what.

[info] weaver.framework.test.MemoisedResourceTests
[error] - Memoised resources should be: 1s
[error]    * lazily allocated,
[error]    * shared when accessed concurrently
[error]    * not finalised until all uses are finished
[error]    * re-allocated on demand after being finalised
[error]  [0] assertion failed (modules/framework/cats/test/src/MemoisedResourceTests.scala:33)
[error]  [0] 
[error]  [0] } yield expect.all(initCount == 3, finCount == 3, useCount == 12)
[error]  [0]                    |         |
[error]  [0]                    4         false
[error] 
[error]  [1] assertion failed (modules/framework/cats/test/src/MemoisedResourceTests.scala:33)
[error]  [1] 
[error]  [1] } yield expect.all(initCount == 3, finCount == 3, useCount == 12)
[error]  [1]                                    |        |
[error]  [1]                                    4        false
[error] Failed: Total 41, Failed 1, Errors 0, Passed 40
[error] Failed tests:
[error] 	weaver.framework.test.MemoisedResourceTests
[error] (cats2_12 / Test / test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 13 s, completed Feb 9, 2022 11:22:14 PM

Sample build: https://github.com/disneystreaming/weaver-test/runs/5133422123?check_suite_focus=true
Another one: https://github.com/disneystreaming/weaver-test/runs/4781690405?check_suite_focus=true

Start with modules/framework/cats/test/src/MemoisedResourceTests.scala, especially the assertion at line 33, and run the MemoisedResourceTests test repeatedly. Compare failures with the linked sample builds to identify the source of the nondeterminism. Done means the test reliably passes while preserving its checks for lazy allocation, concurrent sharing, finalization, and re-allocation.