fix(typescript-axios): fix error if a parameter called 'index' exists

[goatwu1993]

fix #17068

PR #16782 introduced some local variables which does not follow the naming convetion for local var (prefix with localVar). This causes error when the API has a query parameter which conflict name with local variable.

For example. A parameter called 'index' will cause an error, which is quite a common name.

Add the conventional localVar prefix to work around it.

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/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

  (For Windows users, please run the script in Git BASH)
  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*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.1.0 minor release - breaking changes with fallbacks), 8.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.

[goatwu1993]

should fix #17068

[goatwu1993]

orignal pr #16782

[goatwu1993]

@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @topce (2018/10) @akehir (2019/07) @petejohansonxo (2019/11) @amakhrov (2020/02) @davidgamero (2022/03) @mkusaka (2022/04)

[goatwu1993]

Last run failed due to some error cause by axios/follow-redirects for some unknown reason.
force push to rerun tests

[goatwu1993]

@wing328 please kindly approved and review again. Nothing changed except from rebase master and force push

[macjohnny]

can you rebase to the latest base branch?

[goatwu1993]

@macjohnny done.
the test is not passing. however it is likely not the fault of this pr as the test is already not passing now at master branch.

see pr and run
https://github.com/goatwu1993/openapi-generator/actions/runs/7531594343/job/20500492487?pr=3
https://github.com/goatwu1993/openapi-generator/pull/3

already dead three weeks lol
https://github.com/OpenAPITools/openapi-generator/actions/workflows/samples-typescript-axios-echo-api.yaml

[goatwu1993]

Turn out it is the http echo server (test http server) bug.
should use \r\n (CRLF) to changeline in response header but use \r (LF) instead.

[wing328]

@goatwu1993 thanks for looking into the CI issue

We recently made some changes to the http echo server to use \n instead of \r\n for line breaks.

Would you be able to help update the HTTP response parser to use \n as the line break instead when parsing the response from the echo server?

[goatwu1993]

@wing328 as per chatgpt, the response header parsing of axios is handled by nodejs itself when running on nodejs, which only accept crlf as line breaker per http/1.1 spec. As a result, huge customization needed in axios, maybe some hand made adapters or interceptors.

IMO, you should revert the line breaker to crlf to conform http/1.1 spec.