feat: add the --component-renaming-conflicts-severity bundling option

[tatomyr]

What/Why/How?

Added a new --component-renaming-conflicts option for the bundle command to control how naming conflicts are reported when bundling API descriptions with external references.

Reference

Resolves #661 (mostly).

A follow-up to #2541.

Testing

Screenshots (optional)

Check yourself

• Code changed? - Tested with Redoc/Realm/Reunite (internal)
• All new/updated code is covered by tests
• New package installed? - Tested in different environments (browser/node)
• Documentation update considered

Security

• The security impact of the change has been considered
• Code follows company security practices and guidelines

[changeset-bot]

🦋 Changeset detected

Latest commit: 680c35e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@redocly/openapi-core	Minor
@redocly/cli	Minor
@redocly/respect-core	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	78.59% (🎯 78%)	6132 / 7802
🔵	Statements	78.03% (🎯 78%)	6338 / 8122
🔵	Functions	82.31% (🎯 82%)	1247 / 1515
🔵	Branches	70.33% (🎯 70%)	4189 / 5956

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
packages/cli/src/commands/bundle.ts	87.8%	76.66%	100%	87.8%	120-124, 131-135, 153
packages/core/src/bundle/bundle-document.ts	84.21%	90.9%	66.66%	88.88%	73, 92-103
packages/core/src/bundle/bundle-oas.ts	78.94%	75%	100%	78.94%	35, 52-55
packages/core/src/bundle/bundle-visitor.ts	68.33%	63.56%	100%	68.33%	24, 28-36, 41-49, 56, 65, 73, 78-99, 164-176, 193-194, 207-208, 245
packages/core/src/bundle/bundle.ts	94.73%	86.66%	100%	94.73%	90

Generated in workflow #8514 for commit 680c35e by the Vitest Coverage Report Action

[github-actions]

CLI Version	Mean Time ± Std Dev (s)	Relative Performance (Lower is Faster)
cli-latest	3.593s ± 0.053s	▓ 1.01x
cli-next	3.559s ± 0.022s	▓ 1.00x (Fastest)