Rewrite configuration / environment logic using @wuespace/envar

[pklaschka]

Fixes all kinds of glaring problems the previous configuration had, including:

1. problems related to using the same schema for env and DB config parsing,
2. bad testability due to globally static CONFIG object, and
3. bad documentation of configuration variables due to complex structure.

With this, we can also use @wuespace/envardoc to document our env variables.

• Closes Migrate configuration to @wuespace/envar #4
• Closes zBoolString() breaks apart when parsing already boolean values. #8

• main
  • Rewrite configuration / environment logic using @wuespace/envar #10 👈

Copilot reviewed 10 out of 25 changed files in this pull request and generated 3 suggestions.

Files not reviewed (15)

• deno.json: Language not supported
• example.env: Language not supported
• DEPLOY.md: Evaluated as low risk
• README.md: Evaluated as low risk
• compose.yml: Evaluated as low risk
• env.md: Evaluated as low risk
• lib/cli/bump.ts: Evaluated as low risk
• lib/cli/server.ts: Evaluated as low risk
• lib/cli/stats.ts: Evaluated as low risk
• lib/common/additional-managed-namespaces.ts: Evaluated as low risk
• lib/common/asn.ts: Evaluated as low risk
• lib/common/config.ts: Evaluated as low risk
• lib/common/db.ts: Evaluated as low risk
• lib/common/namespaces.ts: Evaluated as low risk
• lib/common/path.ts: Evaluated as low risk

Comments skipped due to low confidence (2)

lib/common/zod-helpers.ts:19

• The toBoolean function should be covered by unit tests to verify that it correctly converts string values to boolean.

export function toBoolean(value: string | undefined): boolean | undefined {

lib/common/zod-helpers.ts:28

• The toNumber function should be covered by unit tests to verify that it correctly converts string values to numbers.

export function toNumber(value: string | undefined): number | undefined {