feat(test): toHaveBeenNthCalledWith + improve some fail messages

[james-elicx]

What does this PR do?

• Implement jest matcher toHaveBeenNthCalledWith.
• Updates that it's supported in the docs.
• Improve fail messages for toHaveBeenCalled + toHaveBeenCalledTimes so that they provide more info that jest failures provide.

.

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

I wrote automated tests

• I included a test for the new code, or existing tests cover it
• I ran my tests locally and they pass (bun-debug test test-file-name.test)

If Zig files changed:

• I checked the lifetime of memory allocated to verify it's (1) freed and (2) only freed when it should be
• I included a test for the new code, or an existing test covers it
• JSValue used outside outside of the stack is either wrapped in a JSC.Strong or is JSValueProtect'ed
• I wrote TypeScript/JavaScript tests and they pass locally (bun-debug test test-file-name.test)

If new methods, getters, or setters were added to a publicly exposed class:

• I added TypeScript types for the new methods, getters, or setters

[Jarred-Sumner]

Thank you

[Electroid]

Does isAnyInt fail for 0?

[james-elicx]

No. The reason I changed it from isAnyInt to isUInt32AsAnyInt was so that it would fail for negative numbers since this matcher is only supposed to accept an argument that is >=0. Jest throws a matcher error for the arg type saying that it expects a non-negative argument, so this aligns the behaviour with how it works in Jest.