Review settings for type vs value imports

[luxaritas]

• When working on our new Nest project, I noticed an issue where when VS Code auto-imported classes for use with dependency injection, it would import them as type-only, even though they needed to be imported as values to be included properly for dependency injection via emitDecoratorMetadata/reflect-metadata. I wound up setting "preserveValueImports": false and "importsNotUsedAsValues": "remove" on that project for now.
• TS 5 has deprecated preserveValueImports and importsNotUsedAsValues in favor of the new verbatimModuleSyntax

Once TS 5 is out (slated for the 14th), we'll need to review this to hopefully ensure:

• Our configuration still works with Vue script setup
• We avoid confusing errors due to auto-imports incorrectly choosing type-only imports
• Module elision still works when it needs to (or determine we don't care if esbuild's tree-shaking is sufficient)