Description

When investigating the usability of the HttpClient symfony package with promises I find myself in a confused spot. There is the HttplugClient which is looking pretty good and itself is not deprecated in any way since multiple major releases.
Reading the HttpClient documentation on the other hand indicates it should not be used and is superseded by the PSR18 client
Http\Client\HttpClient repeats this impression and points to the PSR18 client. Is the HttplugClient really meant to be replaceable (also out of Symfonys perspective) by the psr client which has no promise support?

I am sorry if this issue ends up in a sort of support case which I surely do not want to open here. I hope to find some clarification for the future of the HttplugClient and how it is intended to be used or not. I am also willing to contribute in documentation improvements if you agree it is in a confusing state.

While I can today just create an instance of the HttplugClient no matter of its future I expected to be able to receive a scoped client by its interface like I can do with Symfonys own HttpClient and also the PsrHttpClient.
It results in the default HttplugClient tho and a look into the output of debug:container as well as the FrameworkExtension shows that those are not meant to work together which I really would like to have as a third option.