When an unsupported device is specified during a flutter -d command, fail, and show all devices so users can see that it was connected, but unsupported.

Note the (unsupported) in the device description:

$ flutter run -d 1754b457ae0324670be2493c147bf08bdad86907
No supported devices found with name or id matching '1754b457ae0324670be2493c147bf08bdad86907'.

The following devices were found:
iPhone 4s (mobile)        • 1754b457ae0324670be2493c147bf08bdad86907 • ios            • iOS 9.3.6 13G37 (unsupported)
Chrome (web)              • chrome                                   • web-javascript • Google Chrome 97.0.4692.99

Context: #66696 conflated isSupported with isSupportedForProject. flutter logs -d device should work even when outside of a flutter project. However, unsupported devices (for all projects) should never be allowed to be targeted.

For example, the Chrome device is "unsupported" when the Chrome isn't installed, but it's "supported" and "not supported for project" when the web directory is missing from a project.

Fixes #97331

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.