1. Proposed title of this feature request
Allow AddonDeploymentConfigs to use nodeAffinity

2. What is the nature and description of the request?
Currently, addondeploymentconfigs only allow for nodeselector, which is a hard requirement, but not nodeAffinty, which is a soft requirement
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#scheduling-behavior

3. Why does the customer need this? (List the business requirements here)
They would like to specify pod affinity for ACM addons to ensure they schedule on infra nodes if those nodes exist, specifying a nodeSelector is a hard constraint which is not ideal for clusters where infra nodes don't exist.

4. List any affected packages or components.
RHACM and MCE