Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>

Without this, we get a warning message from Traefik:

> INF Could not create a router for the container: too many services providerName=docker

Possibly due to the multiple services defined there without a single
explicitly-defined router.

Follow-up to 3492d31dca

Communicating via container URLs works, but the URL provided to
livekit-jwt-service as `LIVEKIT_URL` is also passed to the user later
and it must be a public one at that point.

It'd be great if livekit-jwt-service can be given 2 different URLs
(e.g. `LIVEKIT_URL` and `LIVEKIT_URL_PUBLIC`) and only announce the
public one to the user, but there's no support for this yet.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

Fixup related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3442

The new rate limits are more suitable for running Element Call.

Ref:

- 93ae2aed98/docs/self-hosting.md (a-matrix-homeserver)
- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562

Instead of trying to increase them conditionally only when Element Call
is enabled, it's simpler and good-enough to just increase them in all cases.

This is required by Element Call.

Ref:

- 93ae2aed98/docs/self-hosting.md (a-matrix-homeserver)
- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562

This is required by Element Call.

Ref:

- 93ae2aed98/docs/self-hosting.md (a-matrix-homeserver)
- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562