If a project has no "web" folder we don't show the Chrome device, but it's not always obvious why.

It would be nice if we could still show the unavailable devices somewhere (maybe at the bottom of the device selector, with a note like "- unavailable for project") and offer some instructions on how to "upgrade" the project to support this (if appropriate).

It'd be nice if this behaviour was backed by Flutter so we don't need to hard-code rules directly into VS Code.

@jonahwilliams what to you think about getSupportedPlatforms having some flag to include unavailable platforms, but with a flag against them and a reason for why they're not available (at least for those that could be enabled - windows on linux probably doesn't make sense, but web would).