Doc generator reorders properties alphabetically

[krdln]

See eg. https://aperture-tech-docs.netlify.app/docs/development/reference/configuration/policies#v1-rule. Since rego and extractor are required (mutually exclusive) variants of rule, they should go first and optional properties should go last. Now there's a sandwich.

Or see https://aperture-tech-docs.netlify.app/docs/development/reference/configuration/policies#-v1scheduler – the first fields are auto_tokens and default_workload, which require understanding workloads first, which is the last field.

Order of properties in docs should be the same as in definition. See envoy docs. This allows to control the reading order and put more important stuff on front.

This bug was fixed some time ago (https://github.com/fluxninja/cloud/pull/4349) (before moving to github issues), but now I see it was reintroduced.

[DariaKunoichi]

still relevant