enable eslint rules to enforce type import/export style

[josefaidt]

Issue #, if available:

Description of changes:

Enforces consistent type imports and exports. This can help prevent errors such as https://typescript.tv/errors/#ts2742 when consuming the libraries with pnpm or npm's "linked" install strategy.

• enables https://typescript-eslint.io/rules/consistent-type-imports
• enables https://typescript-eslint.io/rules/consistent-type-exports
• enables https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/consistent-type-specifier-style.md
• extends https://github.com/import-js/eslint-plugin-import/blob/main/config/recommended.js
• extends https://github.com/import-js/eslint-plugin-import/blob/main/config/typescript.js

Enabling this emits 504 errors from ESLint

✖ 504 problems (504 errors, 0 warnings)
  504 errors and 0 warnings potentially fixable with the `--fix` option.

Questions:

• how do we feel about the inline type imports? This adheres to "no duplicate imports", but can be rough to sort properly with ESLint (it's easier to sort import type)
• any thoughts on enforcing import order? https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/order.md#options

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 98cb987

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

[edwardfoyle]

This can help prevent errors such as https://typescript.tv/errors/#ts2742

"Can help prevent" or "does prevent"? Do we have a consistent repro where doing this solves the issue?

[josefaidt]

@edwardfoyle I was looking up the original errors I was getting and came across this thread where explicitly using type on imports and exports was the resolution microsoft/TypeScript#47663 (comment)

not sure if this has something to do with it:

Import declarations written with import type, export declarations written with export type { ... }, and import or export specifiers prefixed with the type keyword are all guaranteed to be elided from the output JavaScript.
https://www.typescriptlang.org/docs/handbook/modules/reference.html#type-only-imports-and-exports

I can try resolving these conflicts and linking this to my existing project to see if it gets rid of the type errors