chore: add custom attribute to test and cloud formation template

What was the problem/requirement? (What/Why)

We want to run e2e test in parallel to save time, especially when spinning up a new worker. This however is not easy with current setup and could lead to race condition

What was the solution? (How)

Add custom capabilities for each test to make sure test do not grab worker that's not in scope. Also make some change to the cloud formation template to reflect the newly added custom capabilities.

What is the impact of this change?

We can now research on running test in parallel

How was this change tested?

hatch run cross-os-e2e-test hatch run windows-e2e-test hatch run linux-e2e-test All using the cloud formation template deployment

Was this change documented?

Yes

Is this a breaking change?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

aws-deadline / deadline-cloud-worker-agent