Determine best structure for integration tests across extensions

[timkimadobe]

Linked to adobe/aepsdk-edge-ios#406

Task description

The two main options are:

1. A shared repo that owns all integration tests for extensions, with the test utilities also residing there
2. Integration tests are owned by each respective extension, and they import the test utilities they need

Approaches for each case, in the given scenarios

Running for all extensions

1. Run the integration test repo job
2. Need to have the caller call each repo's integration test job (and handle orchestration, be able to listen for pass/fail, etc)

Running for specific extension

1. Given tests are grouped by extension, run only tests related to specific extension
2. Run the repo's integration test job

Local development

1. Pull the integration tests into local project and run. If changes to integration tests are required, need to go to a separate repo to make updates
2. Run the integration test suite (as it is already part of the project)

Additional implementation details or code snippet(s)

No response

Additional implementation details or code snippet(s)

No response

[emdobrin]

The format has been decided as part of the iOS effort, using the second approach - integration tests are owned by each respective extension, and they import the shared test utilities.