Docker installations should have state.yaml mounted persistently

https://github.com/chrivers/bifrost/blob/8a316ea4a3ffd9510330b65f6677e7e470e5001b/docker-compose.yaml#L7-L10

The current suggested docker compose file doesn't have a persistent mapping for the state.yaml file. Since the state.yaml has the entertainment groups (among other Hue-specific bits) included in it, if the container is recreated that persistent information will be lost.

I've addressed this by copying out the state.yaml from a running bifrost container and then mounting it just like the config.yaml. There may be a chicken-and-egg problem for new installs when the state.yaml does not exist, but I _think_ touching the state.yaml before container creation may fix that.

I believe there are other issues about moving the binary into a separate location than the config, which would allow mounting the subdirectory as a persistent volume, solving this as well.

Thanks for the project! :heart:

Inspect docker-compose.yaml at lines 7-10, where the config.yaml mapping is defined, and review how state.yaml is stored in a running container. Recreate the container using the compose file and verify that entertainment groups and other Hue-specific state persist across recreation without breaking a new installation.

Written by the indexing model from the issue text.