Migration 005 (linter): Enforce version order in linter/test-versions

[saschanaz]

A checklist to help your pull request get merged faster:

• Summarize your changes
• Data: link to resources that verify support information (such as browser's docs, changelogs, source control, bug trackers, and tests)
• Data: if you tested something, describe how you tested with details like browser and version
• Review the results of the linter and fix problems reported (If you need help, please ask in a comment!)
• Link to related issues or pull requests, if any

Fixes #1596

[queengooborg]

Let's wait on #5352, which includes the migration code to clean up the data first? Since this is such a big change, we should stick with the migration process.

[saschanaz]

Yeah, I found there is a prior work, didn't see that 😔. Fortunately not a complete duplicate, though.

[queengooborg]

Couple of other things as well:

• Can we revert the changes to the data itself so that we are only keeping the linter changes? It's a bit challenging to see the changes to the linter itself, not to mention that we will be updating the data in a separate, bulk update PR. (I know this will fail CI, but as Florian has said, it's better for it to fail and show that it's working!)
• We should use the same function for both the linter and the migration/fix script. That way, we're not including two different methods for the same end goal, thus removing redundant lines of code and maintaining consistency.

[foolip]

@saschanaz you might want to weigh in on #5352 as well. The precise rules for what order we require are pretty nuanced, and I think will require a bit of back and forth to get right.

[foolip]

This will need to handle "preview" as well, which didn't exist when you started this lint. That also makes "number" in the name inaccurate.

[foolip]

I think we should use compare-versions to compare versions (with "≤" removed first).

[foolip]

I think there are cases where this lint will require the wrong thing. For example here:

browser-compat-data/api/Element.json

Lines 4501 to 4517 in 445710d

	"firefox": [
	{
	"version_added": "34"
	},
	{
	"version_added": "44",
	"alternative_name": "webkitMatchesSelector"
	},
	{
	"version_added": "3.6",
	"alternative_name": "mozMatchesSelector",
	"notes": [
	"Before Firefox 4, invalid selector strings caused false to be returned instead of throwing an exception.",
	"See <a href='https://bugzil.la/1119718'>bug 1119718</a> for removal."
	]
	}
	],

The webkitMatchesSelector entry is the newest, but we don't want it to be the first one listed. Or maybe we should want that, but then we need to change the rendering rules of MDN, since that will use the first entry.

[saschanaz]

Hmm, now that I'm less active here, I'll drop this in favor of #5352.