test: e2e initialization

[bermuell]

Description

Closes: #1133

Infra work on e2e tests to support testruns against different versions of provider and consumer
Proposed solution allows to define provider version and consumer version to be build and runs local test cases
on the constructed target.
Note: dependeing on the selected versions the tests might fail due to required changes as transformations and not supported checks. A separate PR will be opened targeting compatiblity tests.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• Included the correct type prefix in the PR title
• Targeted the correct branch (see PR Targeting)
• Provided a link to the relevant issue or specification
• Reviewed "Files changed" and left comments if necessary
• Confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• Confirmed the correct type prefix in the PR title
• Confirmed all author checklist items have been addressed
• Confirmed that this PR does not change production code

[p-offtermatt]

Nice work, I really like particularly the way the test target abstracts away so much of the underlying logic.

Some comments, none too major, mostly about adding a bit of documentation.
Could you also please update https://github.com/cosmos/interchain-security/blob/bernd/1133-e2e-compatiblity-tests/tests/e2e/README.md#L14 to match the changed setup? Nothing major, but at least adjust file names

[p-offtermatt]

Hey, there's one more Gosec error, could you please fix it? :) https://github.com/cosmos/interchain-security/actions/runs/7489943947/job/20387679246?pr=1486#step:4:536

[bermuell]

Hey, there's one more Gosec error, could you please fix it? :) https://github.com/cosmos/interchain-security/actions/runs/7489943947/job/20387679246?pr=1486#step:4:536
yes, just pushed the fix + improvement on worktree creation (in case the revision is already checked out) and docker image creation to deal with issues realted to caching.

[sainoe]

Thanks for this work! It's clear and well-integrated into the current infrastructure.
See my comments.

[MSalopek]

LGTM!

I would like to have an option to use pre-built docker images that can just be pulled from a registry. That way we could avoid extraneous build steps an using git worktree.

The released versions don't change so it's safe to push docker images (eg v3.3.0 will never change, all changes will exist in subsequent versions such as v3.3.1, v3.4.0, v4.x.y etc)