Make e2e integration tests more usable by injecting secrets

[krebernisak]

Integration tests, like they are currently set up, are not too usable. We would like to start integration tests for all adapters at once, but how do we then inject a different API key to each one?

One possible solution would be to have a secrets.json configured with all secrets required for integration tests. Then every test can read from there.

For CI runs we could have an encrypted secrets.json.gpg file that gets decrypted and provided to the test suite. Documentation on this workflow can be found here.

Originally posted by @krebernisak in #218 (comment)

[GMSteuart]

@krebernisak has consideration gone into a way of generalizing the creation of mock api requests to be used before working on api key integration development?

Edit: I see that issue 247 addresses this. I will be looking to see if there is an open issue regarding DRY test cases being moved to the root test runner.