Use ECS properties instead of container properties

[jorgee]

Closes #5096

Ports the @tom-seqera implementation in #5391 to AWS SDK v2 implementation.

With the RegisterJobDefinitionModel and ContainerPropertiesModel introduced by @pditommaso, these changes shouldn't affect the xpack as the interface it extends remains untouched.

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	08248ac
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/687e3ff6dbde6c000727cc79

[pditommaso]

Nice, let's test using [e2e prod] in the commit message

[pditommaso]

@jorgee aws tests are failing

[jorgee]

It seems the tests are failing because of the job definition reuse. The old definition is using containerProperties and the new one is trying to override with ecsProperties. If I am not wrong, the job definition is reused if container name and nf-token is the same, isn't it? So, I think we should include something else to the token to ensure both are using the same container or ecs properties.

[jorgee]

Token was basically hashing the result of containerProperties.toString. I have added a fake property ecsMode=true in the new version. If there is a job definition with same values but with the previous version, the token will be different and it will generate a new revision. Now, the job is failing because of CI user role permissions as in the other CI pipelines.