Add warning about Android and ChromeAndroid queries giving unexpected results

Queries like Android >= 5 and ChromeAndroid > 100 does not give expected results, as others have commented, because of the data provided by caniuse/Statcounter.

Any ChromeAndroid query and every Android query since version 5 reports only latest Chrome version. It's not useful at all. Acknowledge the limitation at the browsers table; a recommendation could be added too, promoting usage of the 'Chrome' query instead (since Android 5 -2014- Android webview, Chrome for Android and Chrome desktop are aligned, being the same engine underneath actually, with automatic updates).

I don't ask to fix the query results, not even adding aliases, but I think a warning about this is necessary to avoid problems at the documentation. Maybe even at the console output?

It get worse when used with other tools: they give you different results than expected, with wrong transpilation or with a set of results different than when running 'browserslist' because they already included workarounds to this problem. For example, Babel introduced years ago a set of alias from mobile browsers to their 'desktop counterparts' (which has its own flaws like mapping Android version 7 as Chrome 7, which is not true -- Android 7 released with Chrome 51 as browser and webview, and got updates up to Chrome 119).

Despite how many years this is happening, there is still confusion and bad usage cause of this, and the data from caniuse/Statcounter is not expected to change to become more precise on this targets.