Enable Ton matchers in TypeScript when using expect from @jest/globals

[EhsanMarufi]

Ton custom matchers like toHaveTransaction were previously only available when using the global expect. This PR adds full TypeScript support for projects that import expect explicitly from @jest/globals.

Changes

• Introduced a TonMatchers<R> interface to avoid duplication.
• Augmented both:
  • Global jest.Matchers<R> (for traditional global usage).
  • Module @jest/expect's Matchers<R> (for explicit expect imports).
• Ensured module augmentation is triggered by importing 'expect'.
• No runtime changes; this is a pure typings enhancement.

Motivation

Modern Jest usage, especially in TypeScript projects, often relies on explicit imports like:

import { expect } from '@jest/globals';

Without this update, consumers lose type safety for Ton-specific matchers unless they use the global expect, which can lead to confusion or unnecessary workarounds.

Benefits

• Enables proper typings for Ton matchers when using expect via @jest/globals.
• Improves developer experience and consistency across test styles.
• Avoids the need for local patches, manual module augmentation, or as any casts.

Checklist

• All tests pass successfully (yarn test)
• Code passes linting checks (yarn lint)

[archseer]

I also used something like this:

function tonEquals(a, b) {
  if (a instanceof Address) {
      if (!(b instanceof Address)) return false;
      return a.equals(b);
  }

  if (a instanceof Cell) {
      if (!(b instanceof Cell)) return false;
      return a.equals(b);
  }

  return undefined
}

// Extend expect to support Address and Cell equality
import {expect} from '@jest/globals';
expect.addEqualityTesters([tonEquals]);

This way Jest's matchers will use TON specific matches on recursive matchers too, e.g. toMatchObject

    expect(msg).toMatchObject({ sender: deployer.address })