Adjust SCCs for each POD when deploying attestation operator in OpenShift

As discussed in #33, Security Context Constraints (AKA SCCs) should be fined tuned for each of the PODs when deploying attestation operator in OpenShift.

Why? the reason for that boils down to regulations/compliance in a lot of companies that prohibit the use of already existing SCCs (such as anyuid, which is the one being used currently for OpenShift deployment). However, companies are fine if there are dedicated SCCs for the specific use-cases that also must not be used for anything else.

Start by reviewing the OpenShift deployment configuration and the discussion in issue #33 to identify each operator pod and its current SCC usage. Define dedicated SCCs for the specific pod use cases instead of relying on shared SCCs such as anyuid, then verify the deployment remains functional and the SCCs are not broadly reusable.

Written by the indexing model from the issue text.