Skip validating domain list ability if operator has already read, created, or updated CRD

[rjeberhard]

We have functionality in Main that trails the behavior in CRDHelper and additionally does a list of domains to validate the the custom type is available. Oddly, I could consistently reproduce getting a 404 trying to list domains immediately after creating the CRD. This meant that most customers would see a SEVERE message in the operator's log when the operator was started pointing at a fresh cluster.

Looking at the requirement, we added the domain list as a CRD "presence check" in response to use cases where the operator did not have privilege to read the CRD. We don't actually need this extra check if the operator was able to read, create, or update the CRD.

This PR skips the presence check if the operator was able to read, create, or update the CRD.

[ankedia]

Oddly, I could consistently reproduce getting a 404 trying to list domains immediately after creating the CRD. This meant that most customers would see a SEVERE message in the operator's log when the operator was started pointing at a fresh cluster.
[ANIL] My understanding is that listDomainAsync call will return an empty list if CRD is installed but no domains are created. If so, can we have an explict check for the 404 (HTTP_NOT_FOUND) response code and not log the SEVERE error in that case?

[Response from Ryan] The issue was that we were installing the CRD and then immediately calling listDomainAsync -- this was resulting in a 404, which is the result you get when the CRD is not installed. There appears to be a timing window after the install of the CRD where listDomainAsync will return a 404 even though the CRD is now available.

[ankedia]

LGTM