ci(actions): start minikube & install tackle

[djzager]

This is the first PR with the goal leveraging GitHub Actions to provide the Konveyor organization with a simple and extensible CI/CD platform. Here is a link to the Google Slides where this was presented in the Konveyor Technical Architecture Forum.

tl;dr

• This PR introduces 2 GitHub Actions (start-minikube and install-tackle)
• These actions are run via shell scripts that can be invoked via Makefile for local development
• Shell scripts are intentionally made to be self-contained (no source utils.sh) and idempotent (kubectl apply instead of kubectl create) to make them useful for local development
• These actions (and shell scripts) can be re-used in other Tackle projects that need them for testing (ie. tackle2-addon-windup)

The end goal is to make these scripts useful in the typical development workflow to simplify onboarding new contributors by having well used/tested startup scripts.

[djzager]

I figure that if I can make these scripts work on my extremely slow network. It should be ready for primetime 😎

[fbladilo]

@djzager They look good assuming they've gotten a good round of testing , I have these questions :

• We expect these actions to run (at some point) against PRs posted to the main branch in different tackle2 repos (i.e windup, hub)?

If you can summarize the CI idea on a high level it would be helpful in understanding the pieces as they come in and also clarify the overall goal