tw runs dump defaults to S3 to look for Nextflow log file

[ejseqera]

Running any tw runs dump command with v0.10.3for runs using FSx results in errors because the download looks for the Nextflow log file in an S3 path. Seems to work fine otherwise with older versions of the CLI, such as v0.9.2.

For example, run any pipeline on AWS using FSx:

1. Run nextflow-io/hello using FSx and a path on FSx as the workdir
   

2. Try to retrieve metrics using tw runs dump:

tw runs dump -w seqeralabs/benchmarks -id 11w0QdxuGt2ULY -o 11w0QdxuGt2ULY.tar.gz

3. CLI throws an error when retrieving Nextflow log:

tw runs dump -w seqeralabs/benchmarks -id 11w0QdxuGt2ULY
 -o 11w0QdxuGt2ULY.tar.gz
- Tower info
- Workflow general information
- Workflow metadata
- Workflow load data
- Workflow launch
- Workflow metrics
- Task details
- Workflow nextflow.log

 ERROR: Invalid S3 file path: /fsx/2024-10-barcelona/benchmark-fusion/nf-11w0QdxuGt2ULY.log

System info:

 Details
    -------------------------+-----------------------------
     Tower API endpoint      | https://api.cloud.seqera.io 
     Tower API version       | 1.25.0                      
     Tower version           | 24.2.0_cycle26              
     CLI version             | 0.10.3 (a86eeed)            
     CLI minimum API version | 1.15                        
     Authenticated user      | esha-joshi