refactor: control api context api

[ndr-brt]

Feature Request

Currently we have different classes that implement pretty much the same base logic to interact with a control endpoint:

• DataPlaneSignalingClient
• TransferProcessHttpClient
• RemoteDataPlaneSelectorService
• RemoteDataPlaneClient

these classes represent service in a remote way, and they "should" be an implementation of the Service implementation (like RemoteDataPlaneSelectorService is currently). This way the abstraction will be better understandable (e.g.: use "embed" service implementation when it is registered in the runtime, use "remote" implementation otherwise)

Extracting an http client wrapper that provides out of the box authentication, response codes handling and eventual error parsing (note that all the EDC apis return a list of ApiErrorDetail in case of error) will remove duplication and will make new remote services implementation easier to do.

Which Areas Would Be Affected?

remote services

Why Is the Feature Desired?

design

Solution Proposal

If possible, provide a (brief!) solution proposal.