Update dogfood to ensure packages don't schedule on CI nodes

Currently we don't have strict affinity/scheduling rules in place to keep our BB core/addons packages from scheduling on the CI nodes. This can lead to a lot of resources being taken on those nodes for non-CI workloads.

NOTE: Anchore as of last check required non FIPS nodes, and only our CI nodes are non-FIPS. Going forward we can either:

• ensure only Anchore is allowed on the CI nodes
• (or maybe more ideally) add a non-RHEL, non-CI node to the cluster for Anchore and any other workloads that require this special case

AC:

• Choose a path forward for handling Anchore/other workloads that don't function on RHEL/FIPS nodes
• Update dogfood values/cluster setup to reflect this path forward
• Update dogfood values/cluster setup to restrict the rest of BB Core/Addons to the RHEL nodes