"last 2 versions" (and "defaults") should not include "android 4.4.3-4.4.4"

This technically falls out from how caniuse is representing versions for Android, but I think is worth discussing here since it impacts the defaults query.

Relevant data from caniuse:

"android": {
    "browser": "Android Browser",
    "abbr": "And.",
    "prefix": "webkit",
    "type": "mobile",
    "usage_global": {
        "2.1": 0.00480563,
        "2.2": 0.00823823,
        "2.3": 0.00480563,
        "3": 0.000686519,
        "4": 0.0988588,
        "4.1": 0.0494294,
        "4.2-4.3": 0.214194,
        "4.4": 0,
        "4.4.3-4.4.4": 0.300009,
        "67": 0
    }

The caniuse data is only providing one version covering the time since the Android webview went evergreen in Android 5, even though there have been multiple versions in between, just like Chrome.

This causes browserslist to include 4.4.3-4.4.4 in the last 2 versions (and by association defaults) query even though it doesn’t truly meet the criteria - it just appears to due to how the data is represented.

[ai]

@antross oops, I merge PR but then found a big problem (to be honest, your way is still acceptable, but it will force us to release major update because it can create errors in the tools using Browserslist).

Browserslist must to return only browsers from Can I Use. We can’t return android 67, android 66.

For instance, Autoprefixer will use these browsers to get prefixes data from Can I Use. If we will artificially create android 66, Autoprefixer will not find a browser data and it could cause an error.

Can I ask you to do PR in a different way? In last \d+ versions query we need add a filter to remove android 4.4.3-4.4.4 if \d+ less than latest - firstEvergreenVersion.

[ai]

Don’t worry, you already did a big PR