Initial development goals

Initial goals

[x] To validate inputs
[x] To print seconds awaited for workloads when as finish rolling out.
[x] To support awaiting a specific namespace's workloads
[x] To not inspect all the pods, but only the workloads pods.
[x] To setup some CI tests.
[x] Fix test failure caused by finishing before the restart container check has run once
[x] Support accepting any amount of container restarts
[x] Add image/gif to README
[x] Add npm build to ci to ensure it can build
[x] Release and publish v1.0.0

[ ] Just like a climber competition requires the climber to hold on to the top grip for some seconds, it could make sense to introduce a configuration like this. Its use would mainly be if a workload didn't make use if readinessProbe's or similar as those containers would be considered ready instantly even before they have successfully done their startup sequence.
[ ] Hide command from showing (/usr/local/bin/kubectl get ds,deploy,sts --namespace=)

[ ] Is kubectl rollout status going to be fine with a pod that was started up but then got runtime errors, just because it's originally started up properly? I can test this.
[x] How do we make our release branch / tag look? It is messy to have /dist and extremely messy to have node_modules as well. Can I get this setup without that? Some GitHub docs. I now .gitignore dist / package-lock.json and those are only explicitly written to by CI automation that we can trigger. See CONTRIBUTING.md for details about that.

[x] To have a workflow that can automatically update ./dist based on package-lock.json changes I created some automation described in CONTRIBUTING.md under publish