Deleting a wildcard cert and adding it again results in errors

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
If I delete a wild card certificate from the list of ssl certs so that I can recreate it with new dns credentials (because there doesn't appear to be an edit function so that you can update. credentials or change dns hosts) and then create it again you then get errors in the logs like this:

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-5/fullchain.pem, r) error:10000080:BIO routines::no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

It appears to be trying to use the same directory for the cert that was there before because it appears to think it still exists somehow.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

1. Go to SSL Certificates
2. Delete an existing wildcard cert.
3. Create the same wildcard cert again, but change the dns challenge credentials
4. See error

Expected behavior
Should create a new entry or recreate the folders etc. properly.

Start by reproducing the issue from the SSL Certificates flow with the nginx-proxy-manager:latest Docker image, deleting a wildcard certificate and creating it again with different DNS credentials. Inspect the resulting logs and certificate paths; done means the recreated certificate no longer references the deleted /etc/letsencrypt/live/npm-5 directory and nginx configuration validation succeeds.