Update chef-acme to work with chef 17/ruby 3
Summary
Chef-acme 4.1.4 introduces support for chef 17 and ruby 3.0, so we should look at upgrading, but 4.1.4 also includes a change that perists a private key file in a new /etc/acme
directory. https://github.com/schubergphilis/chef-acme/commit/3139ecee36f7094036b3e168a3e2e7edceca6672
When we put this upgrade into GItLab 14.6 we encountered some errors when uses changed their contact information: #6610 (closed) And we went ahead and reverted the upgrade.
In order to move forward we should look at ways of dealing with the new private key file.
Proposal
Wait for a chef-acme release with https://github.com/schubergphilis/chef-acme/pull/130 included, so we can change the private key location to be /etc/gitlab/ssl/...
Then update to the new version, AND put in handling for clearing the private key file. (Perhaps whenever the contact information changes, or when any of our letsenrypt attributes change).