Make keep containers configurable

[chatton]

Description

When running a full test suite, we need to keep the containers around after a test finishes so as to not interfere with other tests. For local development it can be handy to still clean up containers after a single test.

This PR adds a config value to enable this.

closes: #XXXX

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/).
• Added relevant godoc comments.
• Provide a conventional commit message to follow the repository standards.
• Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
• Re-reviewed Files changed in the GitHub PR explorer.
• Review SonarCloud Report in the comment section below once CI passes.

[sonarcloud]

Quality Gate passed for 'ibc-go'

Issues
18 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[gjermundgaraba]

Awesome! Such a quick turnaround <3

[damiannolan]

Wonder if we should ever consider using https://github.com/spf13/viper for managing the configs and env vars. There's a lot of nice convenience methods for handling bools etc.

I think the config as it exists now works pretty good tho!

[chatton]

Wonder if we should ever consider using https://github.com/spf13/viper for managing the configs and env vars. There's a lot of nice convenience methods for handling bools etc.

I think the config as it exists now works pretty good tho!

definitely worth considering I think! The env configuration is not ideal for local use but I think works nicely in CI, however we can probably get viper working nicely in CI too and not needing to propagate envs the same way we do now.