Swap from Jest to vitest

[r59q]

Jest has become a configuration nightmare, requiring separate compilation configuration in order to work. Upon merging #400 many jest tests broke, mostly regarding svelte and i18n, I was able to fix some of them. It was caused due to an inherent enforcement of CJS , as #400 will change the package module type from ES6 to esnext. Luckily most of the jest tests should be compatible with vitest, so it should be a relatively easy transition

Some of the benefits of vitest compared to jest

• It is faster
• It is designed to work with vite
• It is designed to work with ESM and ECMAScript and thereby much more modern

The core of the issue is top-level awaits. See the following for a reference of the issue kulshekhar/ts-jest#2057. It is marked as closed, but the issue persists as no solution can reliably fix this issue.

NOTE: When attempting to solve this issue, check to see if the issue can be resolved using updates to TS/Jest/ts-jest, etc.