Don't set wiretap if a LoggingHandler exists

[alzimmermsft]

Description

Updates NettyAsyncHttpClientBuilder to ignore the wiretap configuration if a Netty LoggingHandler has already been set. wiretap(boolean) that we use sets a very basic LoggingHandler that doesn't have much nuance to it, so blindly setting this does a disservice to anyone who has passed an existing Reactor Netty HttpClient with a configured logger.

This also marks the wiretap API as deprecated with a recommendation to use the Reactor Netty HttpClient builder with a logger configured.

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

APIView has identified API level changes in this PR and created following API reviews.

com.azure:azure-core-http-netty