Migration to a new iOS http client

Apple has become strict with privacy and AFNetworking seems to have an impact on it.
Users who use that client will be warned by Apple Store:

ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/AFNetworking.framework/AFNetworking”, which includes AFNetworking, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting November 12, 2024, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements.

The library itself has been deprecated and suggests migrating to Alamofire swift library: https://github.com/Alamofire/Alamofire

This is worrying as Apple Store could reject app submissions for such a reason.

Inspect the repository's iOS HTTP client integration and compare its AFNetworking usage with the Alamofire migration target linked in the issue. The work is done when the iOS client no longer depends on the deprecated AFNetworking library and app submissions no longer trigger the cited privacy-manifest warning.