Limit supported versions for checks

[xginn8]

The title was Checks fail on balenaOS 2.3.0 ...with the following error:

Error reported when querying checks data: checks failed: exit code 2 stderr: jq: Unknown option -cn Use jq --help for help with command-line options, or see the jq documentation at http://stedolan.github.com/jq jq: Unknown option -cn Use jq --help for help with command-line options, or see the jq documentation at http://stedolan.github.com/jq jq: Unknown option -cn Use jq --help for help with command-line options, or see the jq documentation at http://stedolan.github.com/jq jq: Unknown option -c

Expanding this a bit, we should decide on what we support for devices going forward, and make this clear.

[xginn8]

@shaunmulligan & @imrehg what are your thoughts on limiting checks to a certain number of deployed devices? ie, aiming to cover N% of devices. currently, the breakdown is as follows:

50% of devices are greater than v2.31.2
75% of devices are greater than: v2.26.0
90% of devices are greater than: v2.9.7
99% of devices are greater than: v2.0.0
99.9% of devices are greater than: v1.24.1

It may not make sense to reconfigure the check logic to support older OSes, and instead just display a notification that the device is too old (thus feeding back into promoting host OS upgrades). The farthest back I can currently provision is 2.11.0+rev1 on the NUC (even from staging), and I can confirm the checks work on that OS version. Perhaps it makes sense for that to be the initial cutoff? That version would cover roughly ~87.826% of devices currently deployed.

[xginn8]

I've put together a demo of what this could look like, if it makes sense (just pretend the version is correct in the screenshot)

[xginn8]

In development, we will only test multicontainer-capable devices and above, but will not limit the UI.

[xginn8]

We can and should display a warning banner in these cases

cc @tmigone

[xginn8]

we now warn in the UI for this condition