feat: add fips-compliant annotation to CSV

[rhdedgar]

Adding features.operators.openshift.io/fips-compliant: "true" annotation to the CSV as per the FIPS Operator checklist.

Closes RHAIENG-1325.

[derekhiggins]

This appears to be openshift specific, I wonder if it should only be in midstream only, although we already have openshift annotations in here so maybe its ok?

[rhdedgar]

Hi, I'm ok either way, it should be a no-op for most purposes upstream. Though the config/manifests/bases/llama-stack-k8s-operator.clusterserviceversion.yaml file gets created when building the operator. It's unused, as far as I can tell, so this just adds the label to that CSV when it does get created.

[VaishnaviHire]

Maybe we just add this in overlays for midstream, since the csv is not part of deployment by default?

[VaishnaviHire]

@mergify rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[VaishnaviHire]

Maybe we just add this in overlays for midstream, since the csv is not part of deployment by default?

/lgtm for this change. But as mentioned here, need to add them in midestream overlays

[rhdedgar]

The e2e tests are failing due to a known issue I'm working on in RHAIENG-1655. The upstream run.yaml config has new requirements, and the example files and e2e test process needs to be updated to match.