Space typos in ERS codes prevents programatic usage

[jfy133]

Describe the bug
Some entries in archive_accession fields have accidently left in spaces which breaks programmatic processing. We should ensure this field does not contain them with a regex in the JSON (or in AncientMetagenomeDirCheck).

Examples are:

SRS3078134, SRS3078129 (in the middle)
SRS3078134,SRS3078129 (at the end)

Additional context
Add any other context about the problem here such as supporting citations or referennces

[maxibor]

For reference, this is the solution:

"archive_accession": {
                "$id": "#/items/properties/archive_accession",
                "type": [
                    "string",
                    "null"
                ],
                "pattern": "[^ ]*",
                "title": "Archive accession number",
                "description": "Samples archive accession numbers, multiple records can be separated with commas. No spaces allowed",
                "examples": [
                    "SRS473742,SRS473743,SRS473744,SRS473745"
                ]
            }

Waiting for another issue to be fixed (#356) to propose it as a PR