import automation in some cases picks up the md5 sum file instead of the fastq file

[aclum]

{
"resources": [
{
"id": "nmdc:dobj-11-wsa33q95",
"type": "nmdc:DataObject",
"name": "52644.1.406928.GTGAGTGA-CTCTGGTT.fastq.gz.md5",
"file_size_bytes": 33,
"md5_checksum": "04eb414d478126b1f1b994ed424cc5c1",
"data_object_type": "Metagenome Raw Reads",
"was_generated_by": "nmdc:omprc-11-zdqkf654",
"url": "https://data.microbiomedata.org/data/nmdc:omprc-11-zdqkf654//global/cfs/cdirs/m3408/ficus/pipeline_products/nmdc:omprc-11-zdqkf654/nmdc:omprc-11-zdqkf654/52644.1.406928.GTGAGTGA-CTCTGGTT.fastq.gz.md5",
"description": "Metagenome Raw Reads for nmdc:omprc-11-zdqkf654"
}
]
}

Fix regex such that md5 file doesn't get picked up. It is picking up this file instead of the raw fastq file specifying this as has_input to reads filtering.

cc @mbthornton-lbl

[AmitBinf]

Changing import_suffix for data_object_type: Metagenome Raw Reads in import.yaml and import-mt.yaml
from --> import_suffix: .[A,C,G,T]+-[A,C,G,T]+.fastq.gz
to --> import_suffix: \.[ACGT]+-[ACGT]+\.fastq\.gz$
should resolve this issue.

\. matches a literal dot (.).

[ACGT]+ matches one or more occurrences of the letters A, C, G, or T.

- matches a literal hyphen (-).

[ACGT]+ matches one or more occurrences of the letters A, C, G, or T again.

\.fastq\.gz matches the literal string .fastq.gz.

$ ensures that the pattern matches only at the end of the string, so it won’t match .fastq.gz.md5

@aclum @mbthornton-lbl

[aclum]

Please submit a PR including an updated test to this effect.