expect, jest-matcher-utils: Improve report when matcher fails, part 9

[pedrottimark]

Summary

For matcher error in:

• .toBeCloseTo
• .toBeGreaterThan
• .toBeGreaterThanOrEqual
• .toBeLessThan
• .toBeLessThanOrEqual

When expected or received must be a number:

• Because matcher name does not include period, display in black instead of dim color
• With options argument, display .not or .rejects or .resolves

In ensureActualIsNumber and ensureExpectedIsNumber functions:

• Support backward compatible [.not] and dim matcher name if it does include period.
• Delete 'This matcher' default for matcherName arg. I doubt it has ever been used.

Residue provide options to ensureExpectedIsNumber calls when we improve spy matchers:

• .toHaveBeenCalledTimes and .toBeCalledTimes
• .toHaveReturnedTimes and .toReturn

Test plan

• jest-matcher-utils: updated 2 snapshot tests and added 6 new snapshot tests
• expect matchers: added 6 new snapshots tests to .toBeCloseTo as integration test
• expect spyMatchers: 48 snapshot tests unchanged backward compatibility (see Residue)

[SimenB]

This is awesome, as always. Thanks!

[jeysal]

Looking good 👍

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.