[EMBR-5846] Fix `URLSessionDelegate` methods forwading based on `responds` and not only conformance

[ArielDemarco]

Overview

This PR addresses an issue where some methods from different NSURLSessionDelegate subprotocols (such as NSURLSessionDataDelegate or NSURLSessionTaskDelegate) may be implemented by the original delegate without explicitly declaring conformance to these subprotocols. Probably, this can work because Foundation likely checks whether the object responds to a selector, rather than strictly verifying if it declares conformance to the protocol.

To resolve this, our implementation now performs a similar behavior. If we detect that the original delegate does not explicitly conform to the expected subprotocol but responds to the relevant selectors, we directly forward the calls to the original delegate. This ensures compatibility with delegates that rely on runtime behavior for method resolution.

[WIP: Missing tests]

[notion-workspace[bot]]

Issue forwarding to NSURLSessionDelegate methods if object doesn’t conform to specific protocol

[github-actions[bot]]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[github-actions[bot]]

	Warnings
:warning:	No CHANGELOG entry added.

Generated by :no_entry_sign: Danger Swift against e782e361fe9a768b74ed339ab3b64db9c9e0ef28