👻 Add CSV annotations

[jmontleon]

I am not certain about this one. Can others weigh in:

features.operators.openshift.io/proxy-aware

Specify whether an Operator supports running on a cluster behind a proxy by accepting the standard HTTP_PROXY and HTTPS_PROXY proxy environment variables. If applicable, the Operator passes this information to the workload it manages (operands).

[rayfordj]

/lgtm

Thanks!

[shawn-hurley]

I have a minor concern that is probably outside the scope of this PR.

We should just do that as a follow on if we decide we are actually fine

[shawn-hurley]

Why are we not designed for fips? Maybe we just need to do the exercise to make sure, but I think we should. @dymurray thoughts?

[rayfordj]

@shawn-hurley , I don't know about "designed for", but we've not yet configured downstream to build to run on FIPS enabled clusters. Until that is done, we should continue to claim "false" for its value. Franco has a task configure and build MTA (7.0.z & 7.1.z) for it , but it is lower priority than other efforts around MTA at the moment.

[rayfordj]

FWIW, we're already injecting this in downstream CSV. This PR just brings the change more visibility and the two CSVs closer parity

[shawn-hurley]

Heard, I just know that a certain class of customers that we probably want to support will only use fips-compliant stuff, so I want to make sure that we can support those folks. If this is tracked elsewhere, then let's go ahead and ignore this for now :)