Remove special handling of 404 status in HTTP client instrumentations

[shakuzen]

This is a tracking issue for all the specific instrumentations that need to be updated. Existing HTTP client instrumentations should be updated to remove the special handling of 404 status responses. This has come up a few times in issues such as #2410. The reasoning for the special handling of 404 and some redirection statuses makes sense for server-side instrumentation but the same reasoning does not apply to client-side instrumentation where the user is in control and responsible for what requests are being made and configuring an appropriate URL mapper. The default URL mapper should provide a safe default (typically returning a constant value for the URL tag), so this change does not affect the default safety, but users who wrote URL mappers relying on the special handling (outside the URL mapper) of 404/etc statuses will need to update their implementation if that handling is what they want.

HTTP client instrumentation to update:

• OkHttp Remove special handling of 404/301 from OkHttp instrumentation #5814
• Jetty Remove special handling of 404 and redirection statuses from Jetty client instrumentation #5825
• Apache HTTP client
• Apache Async HTTP client
• JDK HTTP client

[izeye]

I created #5837 for Apache (Async) HTTP clients and #5838 for JDK HTTP client.