Add support for disabling special handling of "Creator properties" wrt alphabetic property ordering

[siy]

Support for strict property ordering re-applied to 2.12

[cowtowncoder]

Thank you! Apologies for the slow follow up; I just wanted to add a note that I am still following up on this and plan on getting it included in 2.12 (possibly in 2.12.0-rc2). There is bit of a backlog but I have not forgotten. :-)

One thing I'd need to merge this (unless I have asked for it already) is CLA from:

https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf

which is usually easiest to do by printing, filling & signing, scan/photo, email to info at fasterxml dot com. Only needs to be done once, before the first contribution.

[cowtowncoder]

Ok: the change looks good, and once I get CLA I can merge it. I will probably change the name of feature to indicate that it specifically determines whether "Creator properties" get sorted preferentially, but would not override explicit ordering (with @JsonPropertyOrder), but other than that it's fine.
I'll actually go ahead and add one explicit test to verify my understanding here is correct.

[siy]

Sorry for delays. I'll send signed CLA as soon as I'll be able to reach my printer. Unfortunately I'm in the middle of relocation to another town, so it will take a couple days.

[cowtowncoder]

@siy No problem, there is time, thank you for adding an update so I know the state of things.

One thing I have noticed is that some contributors have managed to add signature digitally (getting an image of signature, scanning or probably there's an app for that), paste on pdf document; that's fine for us as well.
So printing part is not absolutely required. I wish we had a better way to handle this in general.

Anyway: thank you for this contribution & we get it merged when we can!

[siy]

I did send signed CLA to mentioned above e-mail address.

[cowtowncoder]

Thank you -- I finally got to merging this, will go in 2.12.0-rc2.

I renamed property to MapperFeature.SORT_CREATOR_PROPERTIES_FIRST (default state true), but logic otherwise should be the same.