fix: Makes sure OpenApi schema required list is sorted

[sezaru]

This is a very simple PR that basically guarantees that an OpenApi schema is always generated the exact same way if the inputs are the same.

Basically, the required list in the schema is not deterministic, since Map.keys() doesn't guarantee the order the data will output. This means that, if you call that function with the same input multiple times, there is no guarantee that it will output the list in the exact same order.

In my specific use case, this is a big issue because I have a cache system where one of the things I use as the key to the cache, is this schema. and since any required list inside the schema doesn't guarantee order, I was having a bunch of cache misses because of that.

This PR fixes that by sorting the list.

Since it is such a minor change, I didn't change any unit tests, I hope that is OK, but I can create some if needed.

Contributor checklist

Leave anything that you believe does not apply unchecked.

• I accept the AI Policy, or AI was not used in the creation of this PR.
• Bug fixes include regression tests
• Chores
• Documentation changes
• Features include unit/acceptance tests
• Refactoring
• Update dependencies

[zachdaniel]

🚀 Thank you for your contribution! 🚀