ci: implement interchaintests

[joelsmith-2019]

Runs Interchaintests in the CI
This YML does not include steps for running interchaintests on a custom cosmos-based chain, but rather a pre-configured chain with interchaintest. I'm not sure if I need to add that documentation to the workflow as Strangelove's projects aren't really focused on building new cosmos chains as far as I know.

[jtieri]

I'm gonna hold off on this one till we get the others merged if that is okay! I'd like to use this as a test when we have the full CI pipeline in place so we can see what a typical CI run will look like on some actual code changes

[jtieri]

had a few comments but otherwise lgtm.

since we are merging this can we delete main.go though? we no longer need that in place since this code will be what we run to test CI. that should also get the linter passing since it complains about fmt.Println

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[joelsmith-2019]

had a few comments but otherwise lgtm.

since we are merging this can we delete main.go though? we no longer need that in place since this code will be what we run to test CI. that should also get the linter passing since it complains about fmt.Println

We're still going to need main.go because a lot of the workflows check for that file. I fixed that linting error by implementing a logger instead.

[jtieri]

looks good! great work on everything Joel!!