Add option for custom knockd config/wake sequence and to enable knockd logging

### Enhancement Type

Improve an existing feature

### Describe the enhancement

This is less about security and more about having autopause ignore port/server scanners.

Current workaround is by shadowing `/tmp/knockd-config.cfg` via docker mounts and require a couple of knocks in a short period in order to wake up.

Start by tracing the autopause knockd setup and the generated /tmp/knockd-config.cfg, then examine how the Docker mount workaround supplies custom behavior. Determine the supported options needed for a custom knock sequence and knockd logging, and verify that scanners do not wake the server while the documented configuration still works.

Written by the indexing model from the issue text.