Explore a pattern to extend ClientMethodMapper

[anuchandy]

Currently, ClientMethodMapper contains logic that should be part of FluentClientMethodMapper. We should define a design pattern that ensures a clear separation of concerns in such scenarios, which can also be applied to other variants of ClientMethodMapper (e.g., ClientCoreClientMethodMapper in core-v2 wip). This pull request lays the foundation for further exploration of this concept.