[BUG] Incorrect interpretation of yaml spec

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

openapi-generator seems to interpret original yaml file incorrectly, therefore producing incorrect models.

Original yaml differs from one getting placed in api/ folder after generation. Generated file uses wrong schemas for $refs:

    Manage_CreateVpsResponse:
      example:
        vps: null
        error: null
      properties:
        vps:
          $ref: '#/components/schemas/Manage_AttachSshKeyResponse_vps'
        error:
          $ref: '#/components/schemas/Manage_CreateVpsResponse_error'
      type: object

# schema definition for clarity
----
    Manage_AttachSshKeyResponse_vps:
      allOf:
      - $ref: '#/components/schemas/Manage_VpsInfo'

Original yaml:

        Manage_CreateVpsResponse:
            type: object
            properties:
                vps:
                    allOf:
                        - $ref: '#/components/schemas/Manage_VpsInfo'
                error:
                    allOf:
                        - $ref: '#/components/schemas/Manage_CreateVpsResponse_Error'

Manage_VpsInfo is a common message that is being used between all other responses. Every object that has vps property should use this message's schema but instead it generates one inline schema object ManageAttachSshKeyResponse_vps and uses it throughout the spec file.

Unfortunately, I cannot provide steps for reproducing this issue since I have no idea in which cases it does manifest itself.
The only thing I've noticed is that the generator takes the first response object alphabetically that has vps property and proceeds to use it instead of valid ones.

openapi-generator version

openapi-generator-cli via latest-release tag from docker-hub

Generation Details

Steps to reproduce

Related issues/PRs

Suggest a fix

Compare the original YAML with the generated file in the api/ folder, focusing on the $ref entries for Manage_CreateVpsResponse and Manage_VpsInfo. A useful resolution should preserve the original shared schema references rather than selecting an inline schema, but reproduction steps are still needed to define and verify the fix.