Bring back parent name prefix for components with same-name conflicts

[Fluf22]

Is your feature request related to a problem? Please describe.

Redocly Bundle used to resolve component same-name conflicts by prefixing them with the parent component name.
Since #2706 and v2.27.1, the behavior changed: Redocly Bundle now adds a suffix incremental ID.

Describe the solution you'd like

Add an option to be able to use either parent component prefixing or incremental ID suffixing.

Describe alternatives you've considered

We tried renaming our component to try to match the previous state from which we could enable the lint rule to forbid same-name components, moving forward. Unfortunately, it greatly reduces composability and reusability of our schemas.

Additional context

We use component names in addition to OpenAPI Generator tooling to generate SDKs, and these name changes would introduce breaking changes in our SDKs.
On the other side, we would be very glad to be able to stay up-to-date with Redocly.

[kanoru3101]

Hi @Fluf22 , thanks for the feedback!

One important note before we consider bringing the prefix back: relying on auto-generated names (prefix- or suffix-based) for SDK generation is risky in general — they can change whenever you add a new $ref or the resolution order shifts, so an unrelated edit could silently rename a component and break your SDK even under the old behavior.

Could you share a minimal example — the conflicting components, the current bundled output, what specifically doesn't work, and what you'd ideally want? That'll let us check whether the previous naming was actually stable for your case, and see if a decorator might be a better fit for enforcing a consistent scheme.