Story: As a user I like to rely on the status information of an Operator object to inform me about potential user errors or error conditions that were reached in one of the related objects so that I do not need to traverse the dependency tree to debug.

Acceptance criteria:

• upstream documentation
• incorrectly specified operator name, channel name, startCSV drives a status condition in Subscription and is surface on the related Operator object
• error conditions of the Install(Plan) are surfaced on the related Operator Object
• error conditions fo the CSV are surfaced on the related Operator Object
• a cluster admin does not need to consult any of the OLM pod logs in order to discover the causes of common error scenarios