feat!: enables sort-keys rule to make sure keys are sorted alphabetically in ascending order

[jbalsas]

This will be a breaking change as it will result in more errors. Right now, if applied to portal, we get:

✖ 150 problems (150 errors, 0 warnings)

[wincent]

My only doubt is whether the Java sorting we do is case-insensitive too; if we do, then we should match that here, otherwise I'd say not. The thing I don't like about case-insensitive mode is that it isn't deterministic; ie. these are both valid:

const a = {
  a: 1,
  A: 1,
}

const b = {
  A: 1,
  a: 1,
}

[jbalsas]

Verified that Java sorting in portal seems to be "partially" insensitive in that this is the ordering I'm seeing:

fooa
fooA
fooa1
fooa11
fooa20
foob
fooB

[jbalsas]

Hey @wincent, I've checked Java sorting and added the result of my observation. I think there's some case sensitiveness built in, which is likely not 100% correct, but it is what it is.

It also looks like numbers are naturally sorted, so I've pushed an additional commit with that.