Enforce order, completeness, and correctness in rule lists

[hudlow]

We have lists of Spectral rules in a couple of places:

• In documentation: https://github.com/IBM/openapi-validator#spectral-configuration
• In code: https://github.com/IBM/openapi-validator/blob/main/packages/ruleset/src/ibm-oas.js

In these lists, we'd benefit from build checks to make sure:

1. Rules are listed in alphabetical order to make rules easier to find and conflicts less likely when adding rules.
2. All Spectral rules are listed and given an explicit default, so we don't miss any when doing a Spectral update.
3. Defaults listed in the documentation are correct.

Additionally, it looks like we may not be listing our custom Spectral rules in the documentation at all, so we probably need to start doing that and enforcing completeness/correctness in that respect as well.