Comment 15 for bug 1893274

Testing this is pretty tricky because it's specific to the setup of Let's Encrypt's production ACMEv1 endpoint which no longer lets people create accounts or obtain certificates for new domains and we hardcoded the server URL.

The way I'd test it is:

1. Obtain a real, trusted certificate from Let's Encrypt's production ACMEv2 endpoint. This is the default server for Certbot.
2. Run a command like `sudo sed -i 's/acme-v02/acme-v01/g' /etc/letsencrypt/renewal/*` to change the saved `server` value from ACMEv2 to ACMEv1.
3. Run `sudo certbot renew --force-renewal`.

Pre-patch, Certbot should crash because it tries to use ACMEv1 (and an account doesn't exist), but post-patch it should switch to ACMEv2 and successfully renew the certificate.