Fix:
If the logbook controller is not started the stop call will fail.
Trying to start it twice fails.

Prevent locks caused by the zmq log handler reaching the zmq's HWM (High
water mark / buffer limit) and causing some components to block until
the buffer is empty (running the zmq handler for instance).
We run the zmq handler in the background all the time to prevent this.

- Resolves: #7222

Due to #7139 (the logbook log centralizer) logs from 3rd party libs are
included in the centralized logs with lots of debug information and we
don't want that.
We use the existing silencer to exclude logs that are not from leap
modules.

- Resolves: #7185

The logger is the first thing to be created and on a first run the
config path won't exist. This way we make sure the path always exists.

Rotate bitmask.log file on each start.

Forward Twisted logs to logging and use logbook to handle logging logs.
Store the bitmask logs on the config folder.

Replace logging.getLogger with custom get_logger.
Remove some unneeded dependencies and reorder other.

- Add a new handler for a zmq/thread-safe log send between components.
- Update the log window to use this new handler.
- Remove old custom handler
  We have implemented a new handler that uses logbook, so this one is no
  longer needed.
- Adapt log silencer to new handler
- Use log file always as default

- Related: #6733