feat: Enable additional values through set_values for cert-manager

[bryantbiggs]

What does this PR do?

• Enable additional values through set_values for cert-manager
• Update cert-manger helm chart to latest version
• Remove default securityContext and use what the default provided by the helm chart https://github.com/cert-manager/cert-manager/blob/master/deploy/charts/cert-manager/values.yaml#L117

Motivation

• Closes cert manager default behavior is to keep certificate after ingress/c… #813
• This change allows for additional values to be set on cert-manager without needing to re-provide the default values in values.yaml. In addition, I have discovered that you can override the values in the values.yaml through set_values. So in the eks-cluster-with-new-vpc, you can see that --enable-certificate-owner-ref=false but in the cert-manager addon the default values.yaml file has --enable-certificate-owner-ref=true. When deployed, the value is as set to --enable-certificate-owner-ref=false which shows that it can override the default values. So this could open up some interesting use cases where we set opinionated defaults for recommendations (i.e. - set pod disruption budget) but users have the ability to override without needing to copy+paste the default values file and modifying

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.

For Moderators

• E2E Test successfully complete before merge?

Additional Notes