Maintenance: have descriptive logs in the integration tests

[dreamorosi]

Description of the feature request

Problem statement
Now that we are running more integration tests (multiple runtimes for each utility) and in parallel it would be beneficial to have logs that explicitly indicate which utility they belong to. This would help troubleshoot faster in case of issues.

Summary of the feature
Currently this is how the log prefix are:

Ideally we could have something like:

[logger:e2e:nodejs14x]
[tracer:e2e:nodejs14x]
[metrics:e2e:nodejs12x]

Code examples
N/A

Benefits for you and the wider AWS community
N/A - this change concerns mainly maintainers.

Describe alternatives you've considered
None / scroll through the logs

Additional context
N/A

Related issues, RFCs

N/A

[ijemmy]

GitHub matrix strategy may be a better approach. It will fix this issue and be more efficient. I'm looking into that.

[dreamorosi]

With the implementation of the matrix strategy merged in #828 we now have a better separation of the tests that makes it immediately clear which logs you're looking at, we can close this issue as resolved.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.