[Feature] ServiceADES implementation

[fmigneault]

Provide a service implementation that combines ServiceAPI and ServiceWPS.
According to the incoming request, the children resource handling could be dispatched to the appropriate service implementation.

With this type, the "same" Process resources represented through OpenAPI (ADES) endpoint or via traditional WPS endpoint would point to the same resource/permission sets, which will make resulting ACL more natural and consistent.

Some mapping of corresponding elements must be accomplished.
For example:

• WPS GetCapabilities request (with query param) must be mapped with corresponding OpenAPI ADES GET /processes.
• WPS DescribeProcess request (with process id param) must be mapped with OpenAPI ADES GET /processes/{id}

Therefore, we must map the resources correctly so that different service implementation handle them as intented
(eg: GetCapabilities points to ServiceWPS itself while /processes is a children of ServiceAPI).
Similarly, permissions must be mapped (eg: GetCapabilities from query parameter of ServiceWPS becomes read permission from GET request for ServiceAPI).

Relates to #183