feat: Add vitest bindings with the same interface as the jest interface, and extract common TS-side user code to a shared package, contract-case-dsl-js, useful for anyone building non-jest or non-vitest bindings

.release-please-manifest.json

@@ -9,7 +9,10 @@
   "packages/case-plugin-base": "0.29.1",
   "packages/case-plugin-dsl-types": "0.29.1",
   "packages/case-entities": "0.29.1",
-  "packages/contract-case-jest": "0.29.1",
+  "packages/contract-case-dsl-js-internals": "0.29.1",
+  "packages/contract-case-dsl-js": "0.29.1",
+  "packages/contract-case-dsl-js-jest": "0.29.1",
+  "packages/contract-case-dsl-js-vitest": "0.29.1",
   "packages/documentation": "0.29.1",
   ".": "0.29.1",
   "packages/contract-case-cli": "0.29.1",

README.md

@@ -45,7 +45,7 @@ Feedback on the ContractCase API / DSL and (especially) naming
 conventions very welcome. However, the following caveats should be kept in mind:
 
 1. ContractCase doesn't currently support merging of contracts. This means that each contract must be defined in one test file (per contract).
-1. ContractCase currently is only compatible with Jest (js/ts) and JUnit (java).
+1. ContractCase currently is only compatible with Jest and Vitest (js/ts) and JUnit (java).
 1. ContractCase currently only has minimal broker support. It supports the Pact
    broker, although the Pact broker isn't able to render ContractCase contracts
    in the UI.