Trigger reconciliation of clusterbuilder

[mgibson1121]

We have observed a number of factors that lead to issues with the builder/ClusterBuilders state that include cached secrets and issues accessing the registry in which a builder image is written to. The builder/ClusterBuilder resource also has a long loop before the kpack controller attempts to re-reconcile the resource. This can lead to frustration on behalf of users where they make me changes to their kpack configuration during troubleshooting, but the reconciliation loop has not yet occurred.

Proposed solution

Introduce a CLI command to forces a reconciliation attempt of builders/Cluster Builders

Acceptance Criteria

• Implement a kpack CLI command accessible from the builder/ClusterBuilder tree of commands to force a reconciliation attempt. Verbs like "kick" or "trigger" are often used in K8s ecosystems for use cases like this.