Update docs for --progress (#360)

* hint: Waiting for your editor to close the file...
Initial checkin of code to check on the progress of deployment.
The deployment will fail if a container failes with ErrImagePull.
State changes of pods and containers may optionally be displayed.

This is an intermedite checkin and is not complete.

* Do not crash if we fail to initiate the progress tracker.

* Remove unnecessary client parameter to newWatcher.

* Remove the ceos4 update.  It intereacts with ceos3 inside the
Kubernetes fake when doing updates.  Update to test changes to
pods.go

* Turn off lint for the nil context test.

* Turn off lint for the nil context test.

* Rename Verbose to Progress

* Move status.go from deploy to pods as it is generic.

* Switch to main's go.mod/go.sum

* Update documentation to include --progress.

docs/create_topology.md

@@ -23,7 +23,8 @@ Usage:
   kne deploy <deployment yaml> [flags]
 
 Flags:
-  -h, --help   help for deploy
+  -h, --help       help for deploy
+      --progress   Display progress of container bringup
 
 Global Flags:
       --kubecfg string     kubeconfig file (default "/path/to/home/{{USERNAME}}/.kube/config")

docs/troubleshoot.md

@@ -30,6 +30,8 @@ For an exhaustive list use the `-A` flag instead of `-n`.
 
 ## Common issues
 
+Use the `--progress` option to monitor the state of the pods as KNE is coming up.
+
 ### Pods stuck in ImagePullBackOff
 
 ```bash
@@ -43,6 +45,8 @@ container image access [steps](create_topology.md#container_images) and then
 delete/recreate the topology. To check which image is causing the issue, use
 `kubectl describe` command on the problematic pod.
 
+KNE should normally detect this condition and fail the deployment.
+
 ### Pods stuck in Init
 
 After creating a topology, some pods may get stuck in an `Init:0/1` state while