confirm tests assert when run within an generator function

[jbolda]

Motivation

We had a few tests that could include a race condition and not actually run any assertions. Add a check to confirm the number of assertions for each test that has this type of pattern. Any test that executes functions and asserts on the return shouldn't require this check.

[VldMrgnn]

Hi Jacob,
Great PR on identifying the tests with potential race conditions—sharp catch! I went ahead and fixed a couple of the tests you pointed out that weren’t actually being executed but were reporting success.
Your attention to detail really highlights an issue that might have gone unnoticed otherwise.

[VldMrgnn]

Following @jbolda's pattern, I noticed that thunk.test.ts was also missing expect.assertions, resulting in at least two tests incorrectly reporting success without actually running. To address this, I’ve added expect.assertions to all tests to ensure the correct number of assertions are made. Consequently, I replaced asserts.assertEquals with expect assertions for consistency and accuracy.