cf update-service should synchronously fail when no associated coa deployment.

[gberche-orange]

Expected behavior

As a coab operator / model author

• in order to quickly diagnose that a service instance is broken and can't be updated
• I need the cf update-service --upgrade command to fail immediately with a meaningful error message

Observed behavior

cf update-service --upgrade gets accepted and fails with a meaningless timeout message:

Showing status of last operation from service my-noop-x-osb-cmdb...

status:    update failed
message:   Execution timeout after 3656s max is 3600
started:   2021-01-26T13:59:44Z
updated:   2021-01-26T15:01:48Z

[gberche-orange]

Alternative fixes:

• check that templates repo properly has an associated deployment
• check that secrets repo has
  • an existing deployment manifest
  • an existing enable-deployment.yml marker