[BUG][Typescript]Generating from multiple yaml files creates conflicting Configuration classes

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• [ N/A ] What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

Hi all. I have a list of yaml files, and i want to generate code for each one of them, and then push that code to separate repositories. My main app imports all these repos and this is where I get a conflict for Configuration and ConfigurationParameters. I'm using typescript-axios as the generator, and I didn't find a way to either exclude the config part from being generated at generator config level, or adding a suffix / prefix to the generated classes (also, at a generator config level).

openapi-generator version

2.3.7

Generation Details

Steps to reproduce

1. have a project with 2 or more yaml files
2. add 2 typescript-axios generators, each with the output pointing to a different folder
3. run openapi-generator-cli with something like openapi-generator-cli generate
4. check the generated folders and observe configuration.ts in both, with the same content

Suggest a fix

There are options for adding suffixes to models and apis, but no option of adding a suffix to configuration files, or omitting them entirely

Start with the typescript-axios generator entry point and reproduce the issue using two YAML files and separate openapi-generator-cli generate runs. Check how configuration.ts and ConfigurationParameters are emitted and how generator options are defined. Done means generated projects can avoid conflicting configuration classes or give them distinct configurable names.