Explicit type annotation for all exports

[paambaati]

Description

When publishing a package auto-generated by openapi-ts to JSR, it complains with this error –

error[missing-explicit-return-type]: missing explicit return type in the public API
  --> /Users/ganeshprasannah/Projects/neon-js-sdk/generated/core/CancelablePromise.ts:83:6
   |
83 |   get [Symbol.toStringTag]() {
   |       ^^^^^^^^^^^^^^^^^^^^ this function is missing an explicit return type
   |
   = hint: add an explicit return type to the function

  info: all functions in the public API must have an explicit return type
  docs: https://jsr.io/go/slow-type-missing-explicit-return-type

error[missing-explicit-type]: missing explicit type in the public API
  --> /Users/ganeshprasannah/Projects/neon-js-sdk/generated/schemas.gen.ts:15:14
   |
15 | export const $Provisioner = {
   |              ^^^^^^^^^^^^ this symbol is missing an explicit type
   |
   = hint: add an explicit type annotation to the symbol

  info: all symbols in the public API must have an explicit type
  docs: https://jsr.io/go/slow-type-missing-explicit-type

JSR, unlike npm, recommends publishing TypeScript code, and will analyze and publish documentation automatically. To be able to do this effectively at scale, JSR recommends explicitly adding type annotations.

Would you folks consider adding this feature, perhaps behind an option flag? Especially considering both Deno (and along with it, JSR) is increasingly being used for production-grade applications, and it would make packages built by openapi-ts very easy to directly publish to JSR.

[mrlubos]

I think this is related to #493

[paambaati]

Closing as duplicate of #493.