Small problems with Caprover

[casparjones]

Since labels that are created in Caprover can no longer be deleted so easily, but only overwritten, I have implemented a few improvements:

• Empty values are skipped, so you can also delete values again in Caprover
• Check whether a "." exists in the key. For testing I had set the name of the job to "false", which led to a parsing error
• To be able to deactivate jobs, I added an enabled to the job, which skips the job if false.

[funkyfuture]

okay, i don't know what a caprover is, so you need to provide information what this is and what actually the problem is when it meets deck_chores. i can't infer that from the provided solutions. also please revert any unrelated formatting changes / apply code normalization with black.