Consider adding capability to disable default wearables

[Luro02]

Given the issues I encountered #104 #105 #106, there were a few times when I would have really liked to implement my own wearable to fix these issues in my code. Then there would be two conflicting wearables, which is not ideal, and I think it would always choose the built-in one over my custom one.

Would therefore be nice to have a way to disable the default ones or override them through for example a priority value that the wearable factory can return to indicate how important it is in case of a conflict.

[DennisMoschina]

As a workaround, you can clone the Flutter library and set the application’s dependency to:

open_earable_flutter:
    path: <path/to/your/clone/of/this/library>

However, I agree that the capability to exclude some wearables would be a valuable enhancement.