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/widget/store/modules/specs/agent/actions.spec.js

@@ -2,8 +2,8 @@ import { API } from 'widget/helpers/axios';
 import { actions } from '../../agent';
 import { agents } from './data';
 
-const commit = jest.fn();
-jest.mock('widget/helpers/axios');
+const commit = vi.fn();
+vi.mock('widget/helpers/axios');
 
 describe('#actions', () => {
   describe('#fetchAvailableAgents', () => {
@@ -27,7 +27,9 @@ describe('#actions', () => {
   });
 
   describe('#updatePresence', () => {
-    actions.updatePresence({ commit }, { 1: 'online' });
-    expect(commit.mock.calls).toEqual([['updatePresence', { 1: 'online' }]]);
+    it('commits the correct presence value', () => {
+      actions.updatePresence({ commit }, { 1: 'online' });
+      expect(commit.mock.calls).toEqual([['updatePresence', { 1: 'online' }]]);
+    });
   });
 });