Browser-compat-data: Sorting of constructors (or any uppercase features)

[Elchi3]

I think something that was confusing to Joe in https://github.com/mdn/browser-compat-data/pull/4552 is that the sorting now sorts in constructors (which are uppercase properties) just like any other (lower-case) property. They've traditionally been put after __compat.

[Elchi3]

Need to decide if we want to go forward with sorting upper-case properties just like anything else or if they should appear first (like they have traditionally)

[Elchi3]

Unfortunately "Foo" sorts in nicely regardless of case. Change it to "Xoo" and then this test fails.
https://github.com/mdn/browser-compat-data/blob/master/test/test-compare-features.js#L19

[vinyldarkscratch]

I'm leaning towards having constructors appear first, as I believe that users will be expecting such a feature at the top. Sorting uppercase features first would be much easier to implement, and we typically avoid uppercase values in the subfeatures.

[a2sheppy]

I feel strongly that constructors must always be at the top, however it's accomplished.

[jpmedley]

I also think constructors should be first.

(I don't care how you implement, but I would note that for constructors name of self === name of parent.)

[vinyldarkscratch]

I've started work on this in #4730, as Migration 003!