Check if a browser supports Custom Tabs before trying to open an URL

[DavidStrausz]

Adds a new method areCustomTabsSupported to the Browser class and uses the method in the BrowserPluginclass to check if any browser on the device can handle opening an URL via Custom Tabs. If no browser can handle it, fallback to opening the URL in the default browser.

I used the exact method suggested in the official documentation. The documentation also suggests to do this check to avoid ActivityNotFoundException exceptions:

If no browser supporting Custom Tabs is available in the device and you launch a URL using customTabsIntent.launchUrl(context, url), the intent might fail, leading to an ActivityNotFoundException.

Always perform a compatibility check to ensure a better user experience.

You can fallback to a standard ACTION_VIEW Intent to open the URL in any available browser.

This will probably fix some of the exceptions mentioned in this issue: #2036