cleanup: remove cluster provisioning from e2e binary

[perdasilva]

Description of the change:
Previously, the e2e test suite would programatically provision a kind cluster and helm install olm on it. This allowed the e2e test suite, which is not stable when executed in parallel against a single cluster, to be executable in parallel (because each test worker would get their own cluster).

Removing the cluster provisioning code has meant that, to keep the parallel execution time gains when executing the e2es, I've had to keep the same strategy of 1 cluster / test node. Therefore, this PR also:

• Refactors the e2e job into more of a pipeline so we're not re-building binaries and images
• Moves the flaky e2e test job into the e2e job
• Simplifies the Makefile removing the e2e spec chunking to the e2e job
• Adds helm-based deploy target
• Refactors the e2e job to provision the test clusters
• Adds kubeconfig-root flag to e2e_test: the directory where the test runners can find the kubeconfig for their cluster
• Adds kind to tools.go
• Removes the kind provisioning and helm installing from the e2e tests

Motivation for the change:
The e2e tests shouldn't care about provisioning their own clusters, etc. They should just be given a kubeconfig and a running cluster.

Architectural changes:

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted