Bug: don't set empty spec.config.resources in subscription

[joelanford]

Due to the way the subscription spec defines the Config and Resources sections as concrete structs instead of pointers, it is not possible to keep them unset. We need to update the operator-framework/api with this change, and then in this repo, require the new version of operator-framework/api that fixes it.

Related issues:

• If resource override is not defined in a subscription then the existing resource definition in the CSV is deleted operator-lifecycle-manager#1912
• Operator deployment resources claimed in CSV aren't passed into the operator deployment operator-lifecycle-manager#1940
• Subscription with empty resource config will overwirte operator deployment resource operator-lifecycle-manager#1953

API PR: TBD
OLM PR: operator-framework/operator-lifecycle-manager#2010

[joelanford]

Fixed in operator-framework/api#97 and closed by #37