[flutter_tools] Fix wireless ADB device discovery when serial contains spaces (#187943)

## Description

When ADB registers a wireless device, it uses the mDNS service name as
the device serial. If there is an mDNS name conflict (e.g. due to
toggling wireless debugging off and on quickly), ADB appends a suffix
like `" (2)"` to the service name, resulting in a serial with a space
(e.g. `adb-SERIAL (2)._adb-tls-connect._tcp`).

Previously, the regex used to parse `adb devices -l` output truncated
the serial at the first space, leading to corrupted device IDs and
"device not found" errors when the tool tried to communicate with the
device.

This change updates the regex in `android_device_discovery.dart` to use
an anchored lazy match that correctly identifies the boundary between
the serial and the state, allowing spaces in the serial.

It explicitly handles the `"no permissions"` state (which is the only
known state containing a space) and uses a generic match (`\S+`) for all
other single-word states.

Detailed comments have been added to the regex to explain this design.

## Related Issues

*   Fixes #187092

## Tests

* Added a new exhaustive test case in
`android_device_discovery_test.dart` (`AndroidDevices can parse various
adb device outputs exhaustively`) that verifies various combinations of
serials (with/without spaces, containing state keywords) and states.
* Ran all tests in
`packages/flutter_tools/test/general.shard/android/android_device_discovery_test.dart`
and they passed.