chore: move jest test to vitest (#130)

### Summary

as suggested by speakeasy:

> Also noticed that your installation of Jest in the SDK repo is causing
an npm audit warning with 1 high severity vulnerability. If you're keen
to switch then I highly recommend [vitest](https://vitest.dev/). It's a
mostly drop-in alternative and requires no config to work. We use it to
test our SDKs.

Also found that its easy to add coverage report just by appending
`--coverage` add the end of the make test commands, but tbd in the
future

### Test
ci should work as before

Makefile

@@ -34,12 +34,12 @@ check:
 ## test-unit:					run unit tests
 .PHONY: test-unit
 test-unit:
-	npx jest --verbose --detectOpenHandles --config jest.config.js test/unit
+	npx vitest --dir test/unit --run --reporter verbose --config vitest.config.mjs
 
 ## test-integration:			run integration tests
 .PHONY: test-integration
 test-integration:
-	npx jest --verbose --detectOpenHandles --config jest.config.js test/integration --forceExit
+	npx vitest --dir test/integration --run --reporter verbose --config vitest.config.mjs
 
 ## test:					run all tests
 .PHONY: test

gen.yaml

@@ -17,9 +17,7 @@ typescript:
       pdf-lib: ^1.17.1
     devDependencies:
       '@types/async': ^3.2.24
-      '@types/jest': ^29.5.12
-      jest: ^29.7.0
-      ts-jest: ^29.1.2
+      vitest: ^2.1.3
     peerDependencies: {}
   additionalPackageJSON: {}
   author: Unstructured