Define the analyses to be delivered according to BALSAMIC tags

[ivadym]

Description

Currently, BALSAMIC delivery can be done using three different flags: balsamic, balsamic-analysis and balsamic-qc. However, the files to be delivered are not clearly defined.

Therefore, and taking into account the analysis output files generated (Clinical-Genomics/hermes#44), it would be convenient to discuss and create new tags (if necessary) based on the well-defined customer's requirements.

This can be closed when:

• A catalog of output analysis files offered to clients has been defined. See following issue.
• The expected output has been associated to the different flags in CG. Only one tag will be used, see comment below.
• The used tags and their associated files have been defined. Only one tag will be used, see comment below.
• The analysis files are successfully uploaded and delivered. @ivadym @keyvanelhami we can check this when deployed

[keyvanelhami]

This issue is related to this issue where the files today are delivered, and what files that we would like to start/stop deliver are summarized.

My suggestions:
Remove balsamic-qc and balsamic-analysis and only use balsamic flag to deliver everything as suggested in here. The reason why we had the different flags, was because we were delivering big files like bam and concat fastq-files. These files are no longer being delivered and the -d balsamic will be sufficient for delivering all files.

We are also going to add a new flag balsamic-umi which will deliver the files related to the balsamic-umi workflow.

[ashwini06]

Decision:
@ivadym : will be implementing the changes in cg for cg deliver -d balsamic, while validation for v9.0 is ongoing

[ivadym]

Closed via #1477.