AWS megatest configuration suboptimal

### Description of the bug During release 5.4.0, we had lots of problems with the pipeline failing on AWS. We need to optimise it so we dont have to monitor (and burn a lot of money/energy on multiple `-resumes`). This was the modification to the configuration I ended up using to ge tthe pipeine to run though: ``` process { maxRetries = 2 errorStrategy = { task.exitStatus in ((130..145) + 104 + 175) ? 'retry' : 'terminate' } withName: 'NFCORE_MAG:MAG:ASSEMBLY:LONGREAD_ASSEMBLY:FLYE' { memory = '128.GB' } withName: 'ALE' { memory = { 36.GB * task.attempt } errorStrategy = 'ignore' } withName: 'PROKKA' { errorStrategy = 'ignore' } } ``` The failing tasks that were ignored either defined by `base.config` or in the profile above were: <img width="1325" height="623" alt="Image" src="https://github.com/user-attachments/assets/14fc64d3-fac7-4a35-867c-107a1bf91ddf" /> ### Command used and terminal output ```console ``` ### Relevant files _No response_ ### System information _No response_