test(logging): fix integration test failures

[phantumcode]

Issue #

Description

• Rework logging integration test to run consistently across iOS, tvOS, and watchOS

General Checklist

• Added new tests to cover change, if needed
• Build succeeds with all target using Swift Package Manager
• All unit tests pass
• All integration tests pass
• Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
• Documentation update for the change if required
• PR title conforms to conventional commit style
• New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
• If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[atierian]

Looks good.

If I'm understanding the change correctly, test runs on different platforms running in parallel shouldn't conflict with each other anymore, e.g:

// run on `main`
// the individual jobs won't conflict with each other
integ_test_logging
   - logging-integration-test-iOS
   - logging-integration-test-tvOS
   - logging-integration-test-watchOS

However, multiple concurrent runs of integ_test_logging can still lead to issues, e.g.:

// run on `main`
integ_test_logging
   - logging-integration-test-iOS
   - logging-integration-test-tvOS
   - logging-integration-test-watchOS

// at the same time, run on `my-cool-feature-branch`
integ_test_logging
   - logging-integration-test-iOS
   - logging-integration-test-tvOS
   - logging-integration-test-watchOS

In this example, for any given platform - logging-integration-test-<platform> run on my-cool-feature-branch can conflict with logging-integration-test-<platform> run on main.

Is that correct?

If so, let's aim to address that in a future PR.