refactor: Rename scanJobsRetryDelay param to avoid confusion

[Elshirak]

Description

Recently I've worked with trivy-operator and was confused because of the difference in naming the same value. In documentation it's called OPERATOR_SCAN_JOB_RETRY_AFTER or similarly, the same is for deploy/helm/templates/configmaps/trivy-operator-config.yaml and deploy/static/trivy-operator.yaml.

Howhever, in deploy/helm/values.yaml the name of the value is scanJobsRetryDelay.

It took some time for me to understand. That's why I suggest using the same value name - scanJobsRetryAfter. What do you think, @chen-keinan ?

• I've read the guidelines for contributing to this repository.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant iblob/main/CONTRIBUTING.md) to this repository.

[CLAassistant]

All committers have signed the CLA.