chore: integrate vitest matchers globally

[starc007]

• closes Integrate vitest matchers globally #3421

Summary

This PR integrates Vitest matchers globally for fuel-gauge tests, improving test maintainability and type safety.

Changes

• Add global setup for vitest matchers in test/setup.ts
• Add proper TypeScript types for custom matcher toEqualBn
• Remove individual expect.extend() calls from test files
• Remove @ts-expect-error comments for toEqualBn usage

Testing

• ✅ All existing tests pass
• ✅ Type checking passes without errors
• ✅ Matcher functionality remains unchanged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ts-docs-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 29, 2024 8:59pm

[CLAassistant]

All committers have signed the CLA.

[vercel]

@starc007 is attempting to deploy a commit to the Fuel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[codspeed-hq]

CodSpeed Performance Report

Merging #3425 will improve performances by 47.93%

_{Comparing starc007:starc007/feat/integrate-vitest-matchers-globally (b142a13) with master (d29e884)}

Summary

⚡ 1 improvements
✅ 17 untouched benchmarks

Benchmarks breakdown

	Benchmark	master	starc007:starc007/feat/integrate-vitest-matchers-globally	Change
⚡	Instantiate from an address	576.7 µs	389.8 µs	+47.93%

[Torres-ssf]

Hey @starc007,

Thank you so much for this contribution. We really appreciate it 🙏

It appears that the current solution hasn’t resolved the TS errors.

[danielbate]

This PR also needs a changeset, please run pnpm changeset from the root directory.

[starc007]

Hey @Torres-ssf

Issue:
When running pnpm lint (type:check-tests), the type checker fails because the matchers aren't being recognized globally. However, when importing setupTestMatchers directly in the test file (e.g. abi-coder.test.ts), it works as expected.

This suggests the setupFiles configuration in vitest.shared.config.mts isn't being properly loaded during type checking.

Questions:

1. Is there a different way we should be configuring the global setup file for both runtime and type checking?
2. Should we be using a different approach to register global matchers that works with the type system?

Any guidance on the correct way to set this up would be appreciated.