feat(httpd/restart): provide a cronjob for rollout restart

[smerle33]

following the last brownout from jenkins-infra/helpdesk#2649
we saw few errors from httpd not handling properly the htaccess content.
This new helm allow to enable an automatic rollout restart of the httpd deployment every hour to ensure httpd file content in pod memories.

we decided to provide a cronjob to restart the pods at pre-defined time (every hours for now), this will lower the impact of that bug. (see jenkins-infra/helpdesk#2649 (comment))

we need to keep in mind that we may need to provide a cleanup for both cronjobs and jobs through the .spec.successfulJobsHistoryLimit and .spec.failedJobsHistoryLimit fields for the first and the .spec.ttlSecondsAfterFinished field for the second

[smerle33]

tested locally on a k3d install:

NAMESPACE            NAME                                       SCHEDULE    SUSPEND   ACTIVE   LAST SCHEDULE   AGE
updates-jenkins-io   updates-jenkins-io-httpd-restart-cronjob   0 * * * *   False     0        <none>          2m54s

[dduportal]

First wave of review. We are in the good direction but some chart element should be updated (a bit of naming, but also default values for some CronJob attributes)