[typescript-axios] / #12828: Add ESM support to typescript-axios client

[miniengineer]

fix #12828

An additional tsconfig.esm.json is added to every generated typescript-axios code having supportsES6 and npmName.
That will create an additional ECMAScript Module (ESM) to the npm build.

I used similar PR for typescript-fetch client as reference #11720

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• File the PR against the correct branch: master (6.1.0) (minor release - breaking changes with fallbacks), 7.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @topce @akehir @petejohansonxo @amakhrov @davidgamero @mkusaka

[miniengineer]

This is my first time contributing to open source 🙇‍♀️

About the following step ⬇️

Run the following to build the project and update samples:
./mvnw clean package
./bin/generate-samples.sh
./bin/utils/export_docs_generators.sh

After running the first command there are some errors, but they are related to the Python client 🤔
I run it while on latest master and I get the same errors, so I assume those are not related to changes in this PR.

When generating samples I also got an error T_T

./bin/generate-samples.sh ./bin/configs/typescript*

Error: Unable to access jarfile /blabla/openapi-generator/modules/openapi-generator-cli/target/openapi-generator-cli.jar

I am sorry, Java is not my first language.
Am I doing something wrong?

[jfeltesse-mdsol]

[miniengineer]

😍 😍 😍 😍

[miniengineer]

UPDATE

I was able to create the JAR file using the following command that skips tests
mvn clean install -Dmaven.javadoc.skip=true -Dmaven.test.skip=true

and successfully generated samples 👍

[macjohnny]

thanks for your contribution!

[miniengineer]

@macjohnny
Thank you for the review 🙏

About removing outDir, as Julien mentioned (and I should've probably added that in the PR description) the reason why I deleted it is because we already supply output directory in the ts config file, so it's redundant in the package.json.

I have successfully build and tested out TS clients on my local 👍