fix: Make livekit use a bindmount for livekit.yml

[Dadadah]

A user mentioned in the dev stoat that they had an issue with livekit config not mounting correctly. Switching livekit to use a bind mount like the other containers should fix that issue.

This pr also makes the livekit container require redis as it uses redis.

[ZeroKnight]

Maybe I'm missing some obscure detail, but ./livekit.yml:/etc/livekit.yml does create a bind mount. Unless the man pages are inaccurate or there's some obscure edge case with compose, these two should be equivalent:

volumes:
  - ./livekit.yml:/etc/livekit.yml
  - type: bind
    source: ./livekit.yml
    target: /etc/livekit.yml

As should the docker-run analogues:

docker run -v ./livekit.yml:/etc/livekit.yml ...
docker run --mount type=bind,source=./livekit.yml,destination=/etc/livekit ...

I'm only guessing here, since I don't know the referenced conversation, but it's possible that the user might have been running into this issue?

[Dadadah]

It was also an effort to make the configuration match existing mounts. Regardless of the end result, we'd rather they match.

[ZeroKnight]

No argument there, consistency is good. FWIW, I think Docker has preferred people use the mount syntax for a little while now anyway. 👍