chore(zero-cache): set log level to info (tldraw#8717)

In order to reduce log volume from the zero-cache fly.io services, this
PR sets `ZERO_LOG_LEVEL` from `debug` to `info` (which is also the
documented default).

Applied to all three deployment templates: single-process, view-syncer,
and replication-manager.

### Change type

- [x] `other`

### Test plan

1. Deploy zero-cache stacks and confirm logs no longer include
debug-level entries.

### Release notes

- Internal: reduce zero-cache log verbosity to `info`.

Author: MitjaBezensek

apps/dotcom/zero-cache/flyio-replication-manager.template.toml

@@ -40,7 +40,7 @@ ZERO_CVR_MAX_CONNS = "__RM_CVR_MAX_CONNS"
 ZERO_CHANGE_MAX_CONNS = "__RM_CHANGE_MAX_CONNS"
 ZERO_LITESTREAM_BACKUP_URL = "s3://__ZERO_R2_BUCKET_NAME/__BACKUP_PATH"
 ZERO_LITESTREAM_ENDPOINT = "__ZERO_R2_ENDPOINT"
-ZERO_LOG_LEVEL = "debug"
+ZERO_LOG_LEVEL = "info"
 DO_NOT_TRACK = "1"
 OTEL_NODE_RESOURCE_DETECTORS = "env,host,os"
 OTEL_RESOURCE_ATTRIBUTES = "service.name=zero-rm,service.namespace=dotcom,deployment.environment=__TLDRAW_ENV,service.version=__ZERO_VERSION"

apps/dotcom/zero-cache/flyio-view-syncer.template.toml

@@ -44,7 +44,7 @@ ZERO_ENABLE_CRUD_MUTATIONS = "false"
 ZERO_UPSTREAM_MAX_CONNS = "__VS_UPSTREAM_MAX_CONNS"
 ZERO_CVR_MAX_CONNS = "__VS_CVR_MAX_CONNS"
 ZERO_CHANGE_MAX_CONNS = "__VS_CHANGE_MAX_CONNS"
-ZERO_LOG_LEVEL = "debug"
+ZERO_LOG_LEVEL = "info"
 DO_NOT_TRACK = "1"
 OTEL_NODE_RESOURCE_DETECTORS = "env,host,os"
 OTEL_RESOURCE_ATTRIBUTES = "service.name=zero-vs,service.namespace=dotcom,deployment.environment=__TLDRAW_ENV,service.version=__ZERO_VERSION"

apps/dotcom/zero-cache/flyio.template.toml

@@ -37,7 +37,7 @@ ZERO_ADMIN_PASSWORD = "__ZERO_ADMIN_PASSWORD"
 ZERO_UPSTREAM_MAX_CONNS = "__SINGLE_UPSTREAM_MAX_CONNS"
 ZERO_CVR_MAX_CONNS = "__SINGLE_CVR_MAX_CONNS"
 ZERO_CHANGE_MAX_CONNS = "__SINGLE_CHANGE_MAX_CONNS"
-ZERO_LOG_LEVEL = "debug"
+ZERO_LOG_LEVEL = "info"
 ZERO_MUTATE_URL = "__ZERO_MUTATE_URL"
 ZERO_QUERY_URL = "__ZERO_QUERY_URL"
 ZERO_ENABLE_CRUD_MUTATIONS = "false"