SentryOptions should use 'HttpMessageHandler' instead of 'HttpClientHandler' to support NSUrlSessionHandler on iOS

[AlexSchuetz]

Problem Statement

The SentryOptions should accept the more general HttpMessageHandler instead of HttpClientHandler to provide to ability to use a custom-configured handler for the HttpClient.

Background:
It is recommended to use NSUrlSessionHandler on iOS (TLS 1.2, performance), but NSUrlSessionHandler only implements HttpMessageHandler.

Since NSUrlSessionHandler inherits from HttpMessageHandler and DefaultSentryHttpClientFactory also mainly uses this class to create the HttpClient, changes are going to be minor.

During creation of the HttpClient the DefaultSentryHttpClientFactory can take care of if it is a HttpClientHandler, a HttpMessageHandler or a NSUrlSessionHandler (which also accepts proxy and decompression properties.

Solution Brainstorm

Going to file a PR.

[AlexSchuetz]

See PR 2503

[bruno-garcia]

Fix merged, we'll close once release is made

[bitsandfoxes]

Released with 3.35.0 🎉