Don't let certain errors fail SPI loading

[alzimmermsft]

Description

Modifies Providers to catch and log LinkageError and ServiceConfigurationError to prevent these errors from failing service provider loading. This is being done as it is possible for implementations of our service provider interfaces to use designs that aren't generally compatible with our support matrix, an example of this is our own JDK HttpClient implementation of the HttpClient service provider which only supports Java 11+ but we base line our Java support on Java 8. It's possible for this to be on the classpath even if the JVM running an application using our SDKs only supports Java 8, and this would cause the application to error out even is another HttpClient implementation, such as our Netty implementation, is also available on the classpath and is valid.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

API changes are not detected in this pull request.