chore: enable tsconfig's verbatimModuleSyntax

[justlevine]

What

Enables TSConfig's verbatimModuleSyntax, which requires types to be imported using the type keyword.

Then remediates all violations of type imports.

Why

Not explicitly marking imported types can cause headaches in consuming projects, ides, incorrect codesplitting and compiling etc.

Related Issue(s):

Part of https://github.com/rtCamp/headless/issues/317

How

Testing Instructions

Screenshots

Additional Info

Interestingly, errors are only caught during npm run build, since npm run typecheck uses the --noEmit flag.

Not sure if this is important, but since our CI builds before it typechecks, I'm personally not bothered by it.

Checklist

• I have read the Contribution Guidelines.
• My code is tested to the best of my abilities.
• My code passes all lints (ESLint, tsc, prettier etc.).
• My code has detailed inline documentation.
• I have added unit tests to verify the code works as intended.
• I have updated the project documentation accordingly.

[justlevine]

If someone could pick this up and fix the ts-jest issues 🙇: https://jestjs.io/docs/ecmascript-modules

[justlevine]

(Rebased on #64)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3fe8635

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[justlevine]

(Rebased on #66)