fix(bupkis): support expect.it() in error-satisfying assertions #342
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

The 'to throw error satisfying', 'to reject with error satisfying', and
similar assertions had special handling for string/RegExp parameters that
bypassed valueToSchema, causing expect.it() functions to fail validation.
Changed the final else-if branch to a plain else clause, letting
valueToSchema handle all non-string/non-RegExp parameters including
ExpectItExecutor functions.
Also expanded property test generators to include expect.it() cases
for better coverage of these assertions.