Service Catalog cleaner should not fail when controller-manager is not deployed

[mszostok]

Bug Report

What happened:
The service catalog cleaner job fails when controller-manager deployment cannot be found. This job is executed as a pre-delete hook.

The problem is that when the svc-cat helm release fails and controller-manager is not installed then release cannot be removed because the cleaner job is executed and fails with not found error.

What you expected to happen:

cleaner job should only ensure that the CRDs and all svcat CRs are removed. With ensure I mean that if they do not exist then it should not fail.

[mszostok]

/assign @gmrodgers

[k8s-ci-robot]

@mszostok: GitHub didn't allow me to assign the following users: gmrodgers.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @gmrodgers

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.