Description of problem:
When both custom runtime and custom workload are specified under the CRI-O configuration, the CRI-O will filter runtime allowed annotation.

Version-Release number of selected component (if applicable):
1.23.0-12.rhaos4.10.git6ee64e9.el8

How reproducible:
Always

Steps to Reproduce:

1. Under the CRI-O config specify
# cat /etc/crio/crio.conf.d/00-default
...

[crio.runtime.workloads.openshift-builder]
activation_annotation = "io.openshift.builder"
allowed_annotations = [
  "io.kubernetes.cri-o.userns-mode",
  "io.kubernetes.cri-o.Devices"
]

# cat /etc/crio/crio.conf.d/99-runtimes.conf
...

[crio.runtime.runtimes.high-performance]
runtime_path = "/bin/runc"
runtime_type = "oci"
runtime_root = "/run/runc"
allowed_annotations = ["cpu-load-balancing.crio.io", "cpu-quota.crio.io", "irq-load-balancing.crio.io"]

2. Create a new RuntimeClass that points to custom runtime
apiVersion: node.k8s.io/v1
handler: high-performance
kind: RuntimeClass
metadata:
  name: performance-manual

3. Create a pod that will use custom runtime and the "cpu-load-balancing.crio.io" annotation
apiVersion: v1
kind: Pod
metadata:
  name: busybox-1
  labels:
    app: busybox
  annotations:
    cpu-load-balancing.crio.io: "disable"
spec:
  runtimeClassName: performance-manual
  containers:
  - image: busybox
    command:
      - /bin/sh
      - -c
      - sleep 600
    name: busybox-2
    imagePullPolicy: IfNotPresent
    resources:
      limits:
        cpu: 1
        memory: 64Mi
  restartPolicy: Always

4. Check under the node via "crictl inspect <container_id>" container annotations


Actual results:
The "cpu-load-balancing.crio.io" annotation does not exist under the container

Expected results:
The "cpu-load-balancing.crio.io" annotation should exist under the container

Additional info:
If I remove the custom workload section from the config, all starts work as expected.