Improve error handling

[EchoEllet]

• The implementations quill_native_bridge_linux and quill_native_bridge_windows don't throw exceptions, instead, they use assertation which will be stripped away in release builds. Should also handle ProcessException in quill_native_bridge_linux.

• We currently don't have a proper way to handle errors, most of the errors are platform-specific and exist for a platform but not for all of them, we need a clean way to handle common errors and platform-specific for each one.

• All errors (except some common errors on Android), are handled in the host platform code but not from the Dart side, you will get an unhandled platform exception PlatformException if an error is thrown.

• It should be clear what kind of expected errors to occur to the caller, enforce error handling will require breaking changes to the quill_native_bridge_platform_interface and all related packages including flutter_quill even if the plugin is experimental. Document the expected errors and when they might happen in quill_native_bridge.

• Part of feat: Use quill_native_bridge as default impl in DefaultClipboardService, fix related bugs in the extensions package singerdmx/flutter-quill#2230