feature: add a timeout on the rollout status watch

[shreddedbacon]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for changelog and subsystem label(s) applied

Sometimes kubectl rollout status can get stuck indefinitely waiting for a rollout to complete due to an issue with the previous pod in the existing replicaset possibly not terminating.

Adding a --timeout=1200s to this status check is double what the progressDeadlineSeconds value is, and if a pod rollout is taking more than 20 minutes to complete, there is probably something wrong anyway.

Closing issues

Partially closes #2861 as it won't actually report on a long running notification, but will prevent the condition where a long running deployment would occur. With intermittent build logs now, it can be more obvious where a build has stalled, before calling it "long running"

[seanhamlin]

Confirming this does what we expect (altered the timeout to be lower for testing):

$ kubectl -n ns-dev rollout status deployment solr --watch --timeout=1m
Waiting for deployment "solr" rollout to finish: 0 out of 1 new replicas have been updated...
error: timed out waiting for the condition

$ echo $?
1