Add Conformance To ClientTransport From swift-openapi-generator

[lilidotshi]

• I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

Problem

Currently Alamofire doesn't have conformance to ClientTransport which is needed if we want to use the new swift-openapi-generator: https://developer.apple.com/videos/play/wwdc2023/10171/

Feature Request

If we want to continue to use Alamofire in conjunction with the swift-openapi-generator, ClientTransport conformance is needed, as we need to supply it to the generated Client as a valid transport type to perform http operations: https://github.com/apple/swift-openapi-generator/tree/7bd8dadd99daafca1ece911209863124a07621f1?tab=readme-ov-file#using-a-generated-api-client

Value to Alamofire

Since this is an apple supported plugin, continuing to use the same Http library is going to be invaluable, and since alamofire is supported by openapi's cli, the next step would be to support it as a part of apple's tools as well.

[jshier]

I've never seen client API generators generate any API code I'd ever want to use, but I'll leave this here in case anyone wants to pick it up as a new feature. It seems rather involved, especially for the streaming version.