[feature request] add support for SRS accession and other kinds of accessions in SRA_Fetch workflow

[kapsakcj]

🆒

📌 Explain the Request

This is an internal request stemming from when a user tried using an SRS accession as input to the SRA_Fetch workflow and seeing a failure.

The tool used, fastq-dl, does support many different kinds of accessions: https://github.com/rpetit3/fastq-dl?tab=readme-ov-file#--accession

But the workflow expects output FASTQ files that are named after the input.

For example if this accession SRS20246375 is used as input, then these 2 FASTQ files (and a metadata file) are output by fastq-dl:

SRR27718943_1.fastq.gz SRR27718943_2.fastq.gz SRS20246375-run-info.tsv

It would be nice to make the WDL workflow as smart as the tool itself and handle these kinds of situations.