No checking for support info order

[connorshea]

On the ServiceWorker page, this happens:

The problem here is that the support array first has the information about Edge 16, where the feature is supported behind a flag, and then subsequently has information about Edge 17, where it's fully supported by default.

The ServiceWorker.json file has these lines:

browser-compat-data/api/ServiceWorker.json

Lines 16 to 29 in 6cad84a

	"edge": [
	{
	"version_added": "16",
	"flags": [
	{
	"type": "preference",
	"name": "Enable service workers"
	}
	]
	},
	{
	"version_added": "17"
	}
	],

The reason this is a problem is because Kumascript assumes that the support array will have the proper support info first, which in this case doesn't happen.

See these lines in kumascript:

// the first entry should be the most relevant/recent and will be treated as "the truth"
checkSupport(supportInfo[0].version_added, supportInfo[0].version_removed);

If we make this assumption, we should try to enforce it with the linter somehow, though I'm not sure how you'd go about doing that. 🤔

Here's an example where it works properly

From the flex page

browser-compat-data/css/properties/flex.json

Lines 44 to 78 in 01c2b6d

	"firefox": [
	{
	"version_added": "20",
	"notes": [
	"Since Firefox 28, multi-line flexbox is supported.",
	"Before Firefox 32, Firefox wasn't able to animate values starting or stopping at <code>0</code>."
	]
	},
	{
	"prefix": "-webkit-",
	"version_added": "49"
	},
	{
	"prefix": "-webkit-",
	"version_added": "44",
	"flags": [
	{
	"type": "preference",
	"name": "layout.css.prefixes.webkit",
	"value_to_set": "true"
	}
	]
	},
	{
	"version_added": "18",
	"version_removed": "28",
	"flags": [
	{
	"type": "preference",
	"name": "layout.css.flexbox.enabled",
	"value_to_set": "true"
	}
	]
	}
	],

[connorshea]

Duplicate of #1596.