Enable verbatimModuleSyntax, fix jest usage

[dannon]

Left this setting hanging around longer than I needed to, but in the vue3 branch we have to resolve it. Following the import fixes in #18589, this can simply be overriden for jest and enabled otherwise -- module syntax is still validated when one builds/works on the client, we can ignore it for jest for simplicity.

Also bumped a few minor jest-related dependencies while digging around.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[davelopez]

Hmmm... some selenium tests in test_stock_tours.py seem to fail consistently... 🤔

[davelopez]

Thank you!

[github-actions]

This PR was merged without a "kind/" label, please correct.

[dannon]

@davelopez Thanks -- the problem here was actually some code that imported types from the api schema, which in turn executed the initial configuration of the fetcher. I figured with your work on openapi-fetch we should just push a resolution for that down the road and make getRoot return the default when used in a context that has no document (i.e. -- the search worker) as a quick fix.