Support using task outputs and configurations as deployables

[erdi]

Currently only files (java.io.File) can be used as deployables. This has certain limitations:

• if the deployable is resolved via a dependency configuration various tricks have to be applied to avoid that configuration from being resolved at configuration time
• if the deployable is an output of a task it means that a dependency between cargo tasks and the task producing the deployable has to be explicitly configured otherwise the deployable won't be built before being deployed