This is, because other recipes might also depend on the presence of the
service.

Previously the Omnibus-provided crond would still run if LetsEncrypt
were enabled and then disabled later. This also goes for the auto-renew
configuration. In both cases, crond is not needed, so we can disable the
service if LetsEncrypt is not used. This also prevents stale
configuration files from lingering.

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5541

* Adds `go-crond` to the build
* Adds a `go-crond` cookbook with a `go_crond_job` LWRP to specify jobs
* Extends the letsencrypt cookbook to use `go-crond` and `go_crond_job`
  resource to trigger the cronned renewal checks
* Adds documentation on how to use/disable the feature