OFO configuration object + flagd upgrade path

[beeme1mr]

usecase

As an operator Given I want to upgrade flagd without upgrading OpenFeature operator Then I should be able to increment configuration and objects to do so.

As an operator Given I want to enable open-feature-operator only on certain nodes Then I should be able to allow for topology keys within a global object.

notes

_I think that adding an operator custom resource to enable upgrading would also allow us to utilize more dynamic global configuration secompprofile on/off, daemonset topology awareness) _

E.g.

apiVersion: core.openfeature.dev/v1alpha1
kind: OpenFeatureOperatorConfiguration
metadata:
  name: default
spec:
  flagvVrsion: v0.26

[beeme1mr]

It may also be worth support a flagdImage property as well. Some organizations may need to pull the image from another artifact repository.