feat: create new pair-to-have-been-called-assertions rule

[nicolasgillot]

Summary

This PR introduces a new ESLint rule pair-to-have-been-called-assertions that enforces using toHaveBeenCalledTimes() or toBeCalledTimes() whenever using matchers like toHaveBeenCalledWith(), toBeCalledWith(), toHaveBeenNthCalledWith(), toBeNthCalledWith(), toHaveBeenLastCalledWith(), or toBeLastCalledWith().

Why?

When testing mock functions, developers often use toHaveBeenCalledWith() to verify that a function was called with specific arguments. However, without also checking the call count, the test can pass even if the mock was called more times than expected, potentially masking bugs.

What does this rule do?

• Requires pairing toHaveBeenCalledWith() (and similar matchers) with toHaveBeenCalledTimes()
• Provides auto-fix that adds the missing toHaveBeenCalledTimes(1) assertion
• Detects contradictory assertions (e.g., toHaveBeenCalledTimes(0) with toHaveBeenCalledWith())
• Works with all call-checking matchers: toHaveBeenCalledWith, toBeCalledWith, toHaveBeenNthCalledWith, toBeNthCalledWith, toHaveBeenLastCalledWith, toBeLastCalledWith

Examples

❌ Incorrect:

expect(mockFn).toHaveBeenCalledWith('arg');

✅ Correct:

expect(mockFn).toHaveBeenCalledTimes(1);
expect(mockFn).toHaveBeenCalledWith('arg');

Resolves #1820