Avoid duplicate deployments for customized needed_services (#371)
Avoid duplicate deployments for customized needed_services (#371)

Closes #353

Since (#344 and) #338 we re-use the `needed_services` dependency tree
to order the deployments steps.

This had an unexpected consequence: "duplicated" services via
customization via `needed_services` also duplicated their deployment.

Customized needed_services make in fact only sense for local execution
as a dependency during `dmake shell/test/run`: it should *not* create
new deployments.

PR #334 + #338 changed the semantic of `dmake deploy`: deployment is
now recursive. We still want that.

This commit resolves all this by following on #338:
- recurse at the deployment level
- but strip service customization in recursion
Deepomatic/dmake,Deepomatic/dmake,Deepomatic/dmake,Deepomatic/dmake