Run go-build on each kubepush and vagrant log only states that change or error to improve readability

There are two problems addressed by this PR:

1. The current vagrant provision output that shows the salt results is too verbose and hard to parse.
2. The Salt SLS for go-build operations was only occuring if the source on disk actually changed.  This had the negative impact of a user doing a cluster/kube-push.sh and getting a compile error, then making a call again to cluster/kube-push.sh and because they made no source edit, salt did not report a job failure because the go-build only ran if the contents on disk changed.  As a result, user thinks they are running latest code, but only running the code that had previously compiled (which is now old).

This PR does the following:

1. minimizes logging to only show errors or state changes.
2. modifies the go-builds driven by our Salt files to always run on each invocation even when source on disk has not changed from previous execution.

Therefore, no more false positives reported by Salt.