Feature Request: Tunable to prevent creation of default backingstore and default bucketclass

[troppens]

Feature request:

NooBaa operator creates default backingstore and default bucketclass:

# oc get backingstore,bucketclass
NAME                                                  TYPE      PHASE      AGE
backingstore.noobaa.io/noobaa-default-backing-store   pv-pool   Rejected   13h

NAME                                                PLACEMENT                                                        NAMESPACEPOLICY   PHASE      AGE
bucketclass.noobaa.io/noobaa-default-bucket-class   {"tiers":[{"backingStores":["noobaa-default-backing-store"]}]}                     Rejected   13h
#

To build an NS-FS based solution, I want to bring-up NooBaa without default backingstore and default bucketclass. To do so I would require a tunable in the NooBaa CR which prevents the creation of those default resources.