[BUG] operationIdNameMappings in openapi-generator-maven-plugin do not work

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?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

operationIdNameMappings in openapi-generator-maven-plugin do not replace operationIDs

openapi-generator version

7.13.0

OpenAPI declaration file content or url

openapi_signature_v1.json

Generation Details

getDocumentaryTypes is generated as getDocumentaryTypesOnServer and getDocumentaryTypesDirectOnWeb, and it should be "getDocumentaryTypes" in both cases

Steps to reproduce

Create a same method in two services with two operationID. You add operationIdNameMappings in openapi-generator-maven-plugin to generate the service client with same name. The methods names generated in the client are the originals, and it should be the defined one in operationIdNameMappings

Related issues/PRs

Suggest a fix

Start with the openapi-generator-maven-plugin handling of operationIdNameMappings and reproduce the report using the attached openapi_signature_v1.json specification. Trace how mapped operation IDs are passed into generation for duplicate operations. Done means both generated methods use the configured name getDocumentaryTypes rather than the original suffixed names.