This is the last feature block for integration with Smartwatch Extensions.

This seems to be due to CapabilityClient not registering a change when a device is moved to/from nearby, among other things. This leads to status not properly switching between CONNECTED, CONNECTED_NEARBY and possibly others.

As per the title, a function to get the status of a watch might be a good idea.

Since we use random UUIDs to generate an ID for each Watch, we'll need a way to tell platform handlers which watches are already known. At this stage, if a platform handler is recreated, all it's UUIDs will be regenerated.

We should either add more options to Result, or use a simple Boolean to indicate success/failure

While there is some code for Tizen support, it's currently not functioning as intended.

We want to completely eliminate the need to use platform-specific libraries, so we should create a system to collect data from platform-specific messages and re-broadcast them in a format we prefer.
For Tizen, we'll need to use this intent
For Wear OS, we'll want to use a WearableListenerService

We'll need to use Huawei-s Wear Engine, more info here: https://developer.huawei.com/consumer/en/hms/huawei-wearengine/