Brad Warren

This PR just wants to list this as a 3rd party plugin. For the other PRs actually adding DNS plugins to Certbot, my initial plan was to leave them open...

> But I do think keeping `:param:` and `:returns:` are nice because they encourage longer, clear descriptions of what is passed in. i agree! i don't want to change this...

see https://github.com/certbot/certbot/issues/10282 if anyone needs additional help after reading that thread, i recommend posting to https://community.letsencrypt.org where there is a larger community of folks that may be able to help

@alex and/or @reaperhulk, just to check, any idea what could be going on here or additional things that could/should be looked into? To be honest, I've been beating my head...

Thanks Alex. * cryptography version stayed the same at 43.0.0. (I figured y'all's rust deps were pinned, but I wasn't sure so thanks for the confirmation there.) * maturin version...

based on the comment at https://github.com/certbot/certbot/pull/10265#issue-2989816621, i'm not sure if we wanted to close this issue or not so i'm reopening for now. ohemorange can close if they wish

sorry i haven't commented on this before, but i wanted to suggest that in the first set of PR(s) here we do just try adding this to the manual, standalone,...

note to self: based on https://github.com/tox-dev/tox/issues/149 and the bulletpoint under https://tox.wiki/en/latest/faq.html#new-features-in-tox-4 starting with "We now discover your package dependency changes", tox 4 thinks it supports this out of the box?...

that and perhaps as a separate issue increase how often `certbot renew` runs. depending on the frequency we choose, i'm not sure we even need exponential backoff or maybe even...

This PR is a start, but as far as I can tell, the code added here is unreachable without further modifications to Certbot. To flag a few other high level...