fix: correct sort order for async API keys and update related tests

[leefreemanxyz]

What/Why/How?

This resolves #2740. AsyncApi definitions will now bundle with a regular order, including the asyncapi: <version> appearing as the first line. This brings the behaviour for bundling for AsyncAPI in line with that of the OpenAPI bundling.

Reference

???

Testing

I've added unit tests and fixed any broken ones.

Screenshots (optional)

Check yourself

• This PR follows the contributing guide
• All new/updated code is covered by tests
• [?] Core code changed? - Tested with other Redocly products (internal contributions only)
• [Nope] New package installed? - Tested in different environments (browser/node)
• [N/A] Documentation update has been considered

Security

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

---

Note

Low Risk
Low risk: changes only affect deterministic output ordering when bundling/joining specs, with coverage via updated unit/e2e snapshots.

Overview
AsyncAPI bundling output is now normalized to a stable top-level key order (ensuring asyncapi appears first), bringing it in line with existing OpenAPI key ordering.

This replaces sortTopLevelKeysForOas with a generalized sortTopLevelKeys that supports OAS2/OAS3 plus AsyncAPI 2/3, updates bundle/join to use it, and adjusts unit tests and AsyncAPI e2e snapshots accordingly. A patch changeset is included for @redocly/cli.

^{Reviewed by Cursor Bugbot for commit f12216b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

🦋 Changeset detected

Latest commit: f12216b

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

This PR includes changesets to release 3 packages

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

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