Change final status check error message to be more concise.

[tejal29]

Relates to #176

Description

In case status check phase fails due to one or more failed deployments, print summary of how many deployments or pods failed instead of printing the error for each failed resource.

there are 2 advantages

• make output concise
• removes duplication of error messages are the individual resource failed message is printed above.

Inspired by @etanshaul suggestion on internal docs.

User facing changes

yes. output changes.

Before
on master when deployments could not be stabilized,

...
Waiting for deployments to stabilize
 - default:deployment/leeroy-app Waiting for rollout to finish: 5 out of 10 new replicas have been updated...
 - default:deployment/leeroy-web Waiting for rollout to finish: 1 old replicas are pending termination...
 - default:deployment/leeroy-app failed. [1/2 deployment(s) still pending] Error: kubectl rollout status command killed.
 - default:deployment/leeroy-web failed. Error: kubectl rollout status command killed.
FATA[0062] following resources are not stable:
resource default:deployment/leeroy-app failed due to kubectl rollout status command killed
resource default:deployment/leeroy-web failed due to kubectl rollout status command killed 
tejaldesai@(master)$

After

on this PR, if deployments are stabilized,

Waiting for deployments to stabilize
 - default:deployment/leeroy-app Waiting for rollout to finish: 5 out of 10 new replicas have been updated...
 - default:deployment/leeroy-web Waiting for rollout to finish: 1 old replicas are pending termination...
 - default:deployment/leeroy-web failed. [1/2 deployment(s) still pending] Error: context deadline exceeded.
 - default:deployment/leeroy-app failed. Error: kubectl rollout status command killed.
FATA[0062] 2/2 deployment(s) failed                       
tejaldesai@(fix_status_check_err_msg)$ 

Next PRs.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes unit tests
• Mentions any output changes.
• Adds documentation as needed: user docs, YAML reference, CLI reference.
• Adds integration tests if needed.

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a example to the examples dir, please copy them to integration/examples
• Every new example added in integration/examples dir, should be tested in integration test

Reviewer Notes

• The code flow looks good.
• Unit test added.
• User facing changes look good.

Release Notes

Describe any user facing changes here so maintainer can include it in the release notes, or delete this block.

[codecov]

Codecov Report

Merging #2930 into master will increase coverage by 0.47%.
The diff coverage is 37.5%.

Impacted Files	Coverage Δ
pkg/skaffold/deploy/status_check.go	53.77% <37.5%> (-2.71%)	⬇️
pkg/skaffold/schema/v1beta10/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1alpha5/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1alpha1/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1beta1/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1beta7/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1beta6/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1alpha3/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/latest/config.go	100% <0%> (ø)	⬆️
pkg/skaffold/schema/v1beta5/config.go	100% <0%> (ø)	⬆️
... and 14 more

[priyawadhwa]

lgtm