AGC cannot handle talking to a WES server that does not encode AWS Batch job IDs into WES task names with a pipe `|` separator

[adamnovak]

As noted here: https://github.com/aws/amazon-genomics-cli/blob/2b93a2cb843bce2945538d06f487886b7efe6707/packages/wes_adapter/amazon_genomics/wes/adapters/BatchAdapter.py#L249-L250

AGC needs to see a | and then an AWS Batch job ID at the end of a task name reported from a WES server it is talking to. This is an AGC-specific WES extension; if AGC is put in touch with a merely standard WES server which reports task names and those names do not follow this format, AGC will crash.

AGC probably ought to learn to handle task names that do not follow this format. A WES server might want to report tasks that have not yet launched, or which were run under the same AWS Batch job as another task, or which were handled entirely by the engine without running a Batch job.