Loads global .env in vite.config to fix vscode extension

[Rotorsoft]

Link to Issue

Closes: #9897

This is the configuration that worked for me locally and using the VSCode extension. I had to disable parallel execution for the extension to be able to run all tests at once. We should continue working on trying to parallelize all tests in the future.

Description of Changes

• Calls dotenv.config() in vitest.confit.ts to fix vscode extension failing to load root .env
• Removes unused env var INIT_TEST_DB
• Passes import.meta to database bootstrapping utils to keep track of caller - just logging now, but can be useful
• Removes vitest global setup. This is not needed since all seeders will bootstrap
• Centralizes parallel files/concurrent behavior in vitest.config

"How We Fixed It"

Test Plan

• Unit tested the FIXME() call.
• CA (click around) tested on local and frack:
  • TODO page

Deployment Plan

Other Considerations

Significant changes

[Rotorsoft]

Yes @timolegros, I'm using this opportunity to remove unused variables and simplify bootstrapping and configuration. Next step is to work on test parallelization (future PR)