feat: Use vitest instead of jest, run all the specs anywhere in app/ folder in the CI (#9722)

Due to the pattern `**/specs/*.spec.js` defined in CircleCI, none of the
frontend spec in the folders such as
`specs/<domain-name>/getters.spec.js` were not executed in Circle CI.

This PR fixes the issue, along with the following changes: 
- Use vitest instead of jest
- Remove jest dependancies
- Update tests to work with vitest

---------

Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>

app/javascript/dashboard/store/modules/specs/account/getters.spec.js

@@ -5,7 +5,7 @@ const accountData = {
   name: 'Company one',
   locale: 'en',
   features: {
-    auto_resolve_conversations: false,
+    auto_resolve_conversations: true,
     agent_management: false,
   },
 };
@@ -38,17 +38,11 @@ describe('#getters', () => {
     const state = {
       records: [accountData],
     };
-    const rootGetters = {
-      getCurrentUser: {
-        type: 'SuperAdmin',
-      },
-    };
     expect(
       getters.isFeatureEnabledonAccount(
         state,
         null,
-        null,
-        rootGetters
+        null
       )(1, 'auto_resolve_conversations')
     ).toEqual(true);
   });