fix(mergeallof): make sure fragment is fully merged

[dotslashderek]

Right now we merge on a fragment at most twice; we have some that require more merge operations to
be fully merged.

Motivation and Context

Issue 10745 (platform) shows that some schemas have a larger allOf nesting tree than we're currently accounting for - we'll cycle through an individual fragment either once or twice (if allOf(s) are still detected) but won't try again after that.

Types of changes

• [ x] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [ x] This PR's code follows as closely as possible the coding style/guidelines of this project.
• I have added error reporting and followed the error reporting guidelines.
• I have added event tracking and followed the event tracking guidelines.
• I have updated any relevant documentation accordingly to reflect this PR's changes.
• I have added automated tests (unit/integration/e2e/other) to cover my changes.
• [x ] All new and existing tests pass locally (excluding flaky CI tests).

[Amjcraft]

Going to trust you here. That ref resolver function is a little hard to read.

I feel this should probably be handled by the _mergeAllOf. Instead of the loop here. But it'll work for a quick fix.

[github-actions]

🎉 This PR is included in version 2.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀