Attempt at renames

[Mpdreamz]

• TransportClient => interface IRequestInvoker
• HttpTransport => interface ITransport
• DefaultHttpTransport => DistributedTransport

[stevejgordon]

Without diving into the details, I took a quick scan of this. I generally like much of the renaming here. I like separating the logical transport concept from the IO detail of invoking the requests.

I'm generally in favour of preferring abstract classes over interfaces on things we may evolve. This change will conflict with some refactoring I've done in my WIP branch to update the OTel instrumentation. For example, ITransport methods will need to accept an optional additional parameter, and I implemented overloads in the abstract class to do this in a non-breaking way. I like that we can evolve the base classes more easily than interfaces.

[Mpdreamz]

In general I like this move to abstract classes with transport specifically though I really miss a covariant interface so base classes can expose the injected concrete configuration rather then the the (abstract) base implementation.

The other was by explicitly naming DefaultHttpTransport DistributedTransport it would be more apt for us to introduce a CloudTransport which does not have to care about any of the distributed nature bits of connecting to multiple nodes. This transport would not necessary need to share anything with base classes.

[flobernd]

LGTM!