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/reports/actions.spec.js

@@ -1,13 +1,12 @@
 import axios from 'axios';
 import { actions } from '../../reports';
-import DownloadHelper from 'dashboard/helper/downloadHelper';
-global.open = jest.fn();
-global.axios = axios;
-jest.mock('axios');
+import * as DownloadHelper from 'dashboard/helper/downloadHelper';
 
-jest.mock('dashboard/helper/downloadHelper', () => ({
-  downloadCsvFile: jest.fn(),
-}));
+global.open = vi.fn();
+global.axios = axios;
+
+vi.mock('axios');
+vi.spyOn(DownloadHelper, 'downloadCsvFile');
 
 describe('#actions', () => {
   describe('#downloadAgentReports', () => {