Added force renewal + --dns-duckdns-no-txt-restore

[devedse]

This should fix:
#3138

@jc21 up to you if this is the right way to fix it.

[nginxproxymanagerci]

Docker Image for build 2 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-3155

Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

[jc21]

Seems fine to me. Let me know if this image works for you.

[devedse]

I'll give it a try. Do you know enough about certbot to be able to explain why my change is needed 😄 ?

[jc21]

Well, no I don't know why not restoring the original TXT record would be the answer to this problem. I fully understand the DNS verifiction process, but I feel that the devs of the duckdns certbot might have a bug there.

[devedse]

I just tried it with the normal unchanged code (:latest image) and it works again... wtf... My guess is that DuckDNS can be in a specific corrupted state or something where we need need to not restore the OriginalTxtRecord???

It might still be good to merge this since it apparently can fix the issue.