Ethereum E2E Tests

So with #12 we now can have an Ethconnect running alongside FireFly. This would enable us to actually test FireFly registration as well as the tokens connectors from #10 and #4. However, we'll need Geth and IPFS nodes to be deployed to `kind` as a dep (similar to Postgres) and then some `curl`s to deploy contracts and what not.

Start with getting Geth / IPFS up in `kind` and then start trying to automate the chart deploy using the full stack. Once that's in place we could then add a `git checkout` of the firefly repo to run an e2e test against the whole thing and confirm it works.

This will likely have to be separate from the integration tests that run via `ct` and the values files with `ci/`. Those IT tests should probably enable Ethconnect (using the predeployed Geth but w/ no smart contracts deployed yet) and the tokens connectors so that IT tests ensure the Docker images exist, the K8s resources are valid and deployable, and things don't crash by default.

Then the E2E test can handle taking a fully deployed stack and confirm its not just up but functioning properly too.

Start with the existing ct integration tests and the values files under ci/. Define how Geth and IPFS should run in kind, then trace how the full chart stack could support FireFly registration and token-connector checks. Done means a separate end-to-end flow confirms the deployed stack is functioning, while the integration tests still validate default deployment behavior.

Written by the indexing model from the issue text.