Split all developer tooling configurations into a separate set of internal (kinda) packages

[KTrain5169]

These include the following:

• tsconfig.base.json (Still unsure about if the other tsconfigs are applicable or if each repo should have their own, but at the very least the one that is used as a base should be split.)
• eslint.config.mjs (We have 2 options here: write it as an eslint plugin or just keep the entire object as it is and simply export it)
• .vscode-test.mjs and src/test/test_utils.ts (Only partially since other extensions might not have web versions/may not use all test utils)
• esbuild-configs (This one might actually be one of the easiest to do)
• .husky scripts (This might be going a bit too far, and also I am personally unsure of wanting to make the script the same across absolutely everything.)
• scripts (These are of various usefulness if exported. Most notably, splitting check-malicious-packages.js is separately tracked at Move check-malicious-packages script to be in a separate/different repo & modify for reusability #165 to be more useful after incidents happen, and esbuild.mjs is a file that should not be exported as it's a repository-specific file. Also, these scripts should have bin fields in their package.json so that we don't have to point to a path in node_modules to execute them.)

[KTrain5169]

I have the set up for this ready, I just need to figure out some issues and set up CI publishing.