Don't check if intent is declared by app before launch

[emmauss]

What does the pull request do?

In general, on newer android apps, Google recommends that any intent an app will launch be declared at build time in the apps manifest. Apps then check availability of app that can handle that intent before launching. This avoids having to write exception handlers to catch failed intents.
This works fine for normal apps with limited scope. But for a general purpose app framework like Avalonia, it limits the types of applications it can create. File managers, browsers and text editors may not know at build time all the possible intents a Uri could support. In this case, simply starting the intent, catching any exception that may be thrown from missing activities and hoping the user has an app to handle it is more preferable.

For security reasons, it's still recommended for apps to declare intents they use when they can.

What is the current behavior?

What is the updated/expected behavior with this PR?

No longer try to resolve whether an intent can be handled by an activity, but instead try to start an activity anyway and catch expected errors from wrong intents or missing activity.

How was the solution implemented (if it's not obvious)?

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Fixes #17265

[avaloniaui-bot]

You can test this PR using the following package version. 11.3.999-cibuild0053481-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]