devFlags should not default to empty objects

[strangiato]

Is your feature request related to a problem? Please describe.
When creating a new DSC such as the following:

apiVersion: datasciencecluster.opendatahub.io/v1
kind: DataScienceCluster
metadata:
  name: default
spec:
  components:
    codeflare:
      managementState: Removed
    dashboard:
      managementState: Managed
    datasciencepipelines:
      managementState: Managed
    kserve:
      managementState: Removed
    modelmeshserving:
      managementState: Managed
    ray:
      managementState: Removed
    workbenches:
      managementState: Managed

After the object is created, the operator automatically adds the devFlags as an empty object for all components:

apiVersion: datasciencecluster.opendatahub.io/v1
kind: DataScienceCluster
metadata:
  name: default
spec:
  components:
    codeflare:
      devFlags: {}
      managementState: Removed
    dashboard:
      devFlags: {}
      managementState: Managed
    datasciencepipelines:
      devFlags: {}
      managementState: Managed
    kserve:
      devFlags: {}
      managementState: Removed
    modelmeshserving:
      devFlags: {}
      managementState: Managed
    ray:
      devFlags: {}
      managementState: Removed
    workbenches:
      devFlags: {}
      managementState: Managed

Describe the solution you'd like
devFlags should not default to empty objects when none is provided. They should only appear when the option is provided by a user.

Describe alternatives you've considered

Additional context
devFlags are not a feature that will ever be allowed on a supported version of a DSC and are an advanced feature only intended to be used in testing scenarios. They should not be present in most systems and should not be defaulted.

[AjayJagan]

Migrated to JIRA: https://issues.redhat.com/browse/RHOAIENG-487, hence closing it here.