Add timeout evaluation configuration in policies CRDs

[jvanz]

Recently an user run into issue when the audit scanner starts in a environment with scarce resources. He was running the env-var-secret-scanner policy witch due the dependencies it has to perform secrets scanning it take a little bit longer to run. As the policy server has not that many resources available, all the policy evaluations starts to take longer and eventually, the secret scanner policy hit the policy evaluation timeout. Causing the evaluation to fail.

To workaround the issue, the user reduced the number of parallel request performed. To be less aggressive in this environment with less computational resources. But this is not ideal.

The goal of this issue is to consider allowing define evaluation timeout per policy. Therefore, different policies running in the same policy server can have different evaluation timeout.

Acceptance criteria

• Decide if this should be implemented
• If decided to add this feature, do it!