[swift5] Upgrade to Alamofire 5

[jfrtree]

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

Upgrade swift5 Alamofire dependency to AF5

Describe alternatives you've considered

Considered writing an Alamofire5 RequestBuilder into my project. But if support/interest in Alamofire is on the decline, it may make sense just to move to URLSession

Additional context

[wing328]

@jfrtree thanks for offering help on this. We definitely welcome PRs to update Alamofire to the latest stable version.

[4brunu]

@jfrtree just curious, why do you want to use alamofire instead of URLSession?

Honestly alamofire is there just because of legacy reasons, it was there before so I kept it.

But since URLSession was introduced in the Swift generator, I can't see any use case where it would be better to use alamofire instead of URLSession.

I was even thinking in proposing to remove alamofire from the Swift generator.

[muellnes]

@4brunu I definitely would also prefer to always have the URLSession implementation, so that in the best case you do not introduce any dependencies with the generated API code.
Except for Alamofire still being the most used Swift REST library I would also favor for various other reasons this to be an option like it is now e.g. Alamofire/UrlSession

Compared to plain URLSession there are also still some advantages of using Alamofire, like:

• cURL Command Output
• Dynamically Adapt and Retry Requests
• TLS Certificate and Public Key Pinning
• Network Reachability

[4brunu]

@muellnes thanks for your feedback.

Based on your feedback, I think it's valuable to keep the Alamofire and upgrade it.

[4brunu]

I created #10292 that should fix this.
@muellnes @jfrtree could you please test it in your projects to see if it's working?
Thanks

[muellnes]

@4brunu Thank you for integrating alamofire version 5.4.3. For me everything did work as expected with the latest changes.