Figure out a certbot flow that doesn't involve commenting things out in `docker-compose.yml`

[cincodenada]

Is your feature request related to a problem? Please describe. The current setup advised in docs requires having uncommitted changes to docker-compose.yml, which is awkward and causes issues with conflicts when there are changes to docker-compose.yml. We should avoid that if possible.

Describe the solution you'd like Ideally, I'd like to not need any uncommitted changes as a matter of course. I haven't thought it through totally, but ideally we could detect that certbot has done its initial setup somehow, so the user didn't have to do anything, but it would be reasonable to have a CERTBOT_HAS_RUN=False or something in the environment variables as a fallback.

Describe alternatives you've considered We could also stash changes and pop them as part of ./bw-dev upgrade, but that seems like it's just asking for trouble, and is more invasive than I'd expect for that kind of command.

Additional context Matrix conversation

[mouse-reeve]

I think this relates to https://github.com/bookwyrm-social/documentation/pull/47/files