Review and fix dro and uds task and pipeline design

[alequint]

Fix provided for #1146 is a work around that we must revisit

We are making dro role accept an action that it does not support, to be then skipped afterwards. That is because uds_action is passed today to both uds and dro task steps, which is also a poor design given that these tasks are mutually exclusive.

Suggested Solution:

• Create a Tasks in CLI to cover dro: today we have only one here covering uds. Then move dro step to the new task
• Create a taskdef to invoke new dro task and add it into install and install-with-fvt pipelines. Add a when clause in dro taskdef to guarantee it runs only when uds_action is install-dro
• Add a when clause in uds taskdef to guarantee it runs only when uds_action is install
• Remove install action as a valid one from dro role (i.e. revert the workaround)