Description of problem:

2 EC errors in hypershift-cli.

✕ [Violation] quay_expiration.expires_label
  ImageRef: quay.io/redhat-user-workloads/crt-redhat-acm-tenant/hypershift-cli-mce-29@sha256:9e8b151d32c43638e8918d80407fb6c1cb49f303baa3612c6e98ac27aaf6de89
  Reason: The image has a 'quay.expires-after' label set to '5d'
  Title: Expires label
  Description: Check the image metadata for the presence of a "quay.expires-after" label. If it's present then produce a
  violation. This check is enforced only for a "release", "production", or "staging" pipeline, as determined by the value of the  
  `pipeline_intention` rule data. To exclude this rule add "quay_expiration.expires_label" to the `exclude` section of the policy
  configuration.
  Solution: Make sure the image is built without setting the "quay.expires-after" label. This label is usually set if the
  container image was built by an "on-pr" pipeline during pre-merge CI.

✕ [Violation] quay_expiration.expires_label
  ImageRef: quay.io/redhat-user-workloads/crt-redhat-acm-tenant/hypershift-cli-mce-29@sha256:4d58b2d5907ed477284f1b6a3cbef493340d194d3d62abf11a85faebbb1779a7
  Reason: The image has a 'quay.expires-after' label set to '5d'
  Title: Expires label
  Description: Check the image metadata for the presence of a "quay.expires-after" label. If it's present then produce a
  violation. This check is enforced only for a "release", "production", or "staging" pipeline, as determined by the value of the
  `pipeline_intention` rule data. To exclude this rule add "quay_expiration.expires_label" to the `exclude` section of the policy
  configuration.
  Solution: Make sure the image is built without setting the "quay.expires-after" label. This label is usually set if the
  container image was built by an "on-pr" pipeline during pre-merge CI.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: