Rename FlexibleHttpClient

[sagikazarmark]

As per @dbu's concerns in one of the PRs.

His proposition is HttpSyncAsyncClient which sounds a little bit weird to me.

Any input?

[dbu]

i was not aware that the client was already merged and not added in that PR. given that, i can live with keeping the name. i just felt the name is not really telling what this is. "flexible" is a very broad term...

if we find a great name to express that the client wraps any client and makes it work with both sync and async interface, we could rename this (with BC code of course) but just rename it to some other weird name is no improvement.

[sagikazarmark]

There was no release since the PR got merged, so we are free to change.

[joelwurtz]

UltimateHttpClient

[sagikazarmark]

Closing this for now as no better ideas.