infra: vitest package updates

[GregOnNet]

solves #28

[seangwright]

I noticed some warnings in the CI run for the unit tests.

example:

 ✓ test/result/result.spec.ts (29 tests) 11ms
stderr | test/maybeAsync/maybeAsync.spec.ts > MaybeAsync > hasValue > returns a resolved Promise of true when there is a value
Promise returned by `expect(actual).resolves.toBe(expected)` was not awaited. Vitest currently auto-awaits hanging assertions at the end of the test, but this will cause the test to fail in Vitest 3. Please remember to await the assertion.
 ✓ test/maybe/maybe.spec.ts (22 tests) 13ms
    at /home/runner/work/typescript-functional-extensions/typescript-functional-extensions/test/maybeAsync/maybeAsync.spec.ts:87:26

Could we resolve these with the Vitest updates?

[GregOnNet]

@seangwright Good catch.

I executed the tests locally and applied fixes in maybeAsync.spec.ts.

[GregOnNet]

I also specified "type": "nodule" in package.json due to a warning coming from vite.

[seangwright]

@GregOnNet I had left the "type" property out of the package.json because of complexities I was concerned about with #3, however the nodejs ecosystem has matured since then and it looks like NestJs supports ESM packages as well... so maybe we can also simplify the build in the next release.