fix(cli): fatal on config parse error and use env for postgres log

[geovannewashington]

What changed?

• log.Error replaced with log.WithError().Fatal() on config parse
  failure to prevent execution continuing with a nil config.
• Added POSTGRES_LOG_LEVEL and POSTGRES_LOG_VERBOSE to the config
  struct, replacing the hardcoded values in pgoptions.Log().
• Added SHELLHUB_POSTGRES_LOG_LEVEL and SHELLHUB_POSTGRES_LOG_VERBOSE
  to .env and wired them through docker-compose.yml.

Why

Config parse errors were silently ignored, leading to a nil pointer
dereference on the next line. The postgres log options were also
hardcoded with no way to control them from the environment.

How to test

1. Start the environment with ./bin/docker-compose up -d
2. Set SHELLHUB_POSTGRES_LOG_VERBOSE=notabool in .env.override
3. Run ./bin/cli user ls and confirm a fatal log is printed
4. Revert the override and run ./bin/cli user create followed by
   ./bin/cli user ls to confirm normal operation
5. Verify env vars with ./bin/docker-compose exec cli env | grep POSTGRES

[github-actions]

Claude finished @geovannewashington's task in 4m 50s —— View job

---

Code Review Complete

Reviewed 3 files across code quality, security, testing, Go patterns, and architecture — no issues found. The code looks good as-is.

Summary of what was verified:

• The log.Error → log.WithError(err).Fatal fix correctly prevents nil-pointer dereference from continuing with a failed config parse.
• New PostgresLogLevel / PostgresLogVerbose config fields are properly wired through .env → docker-compose.yml → cli/main.go, with safe defaults matching the env naming convention of existing fields.
• The envs.ParseWithPrefix("CLI_") fallback via MultiLookuper correctly resolves the unprefixed env vars set in docker-compose.yml (consistent with how POSTGRES_HOST, POSTGRES_PORT, etc. are already handled).
• logrus.ParseLevel validates the level string internally; invalid values propagate through pg.New and are caught by the existing fatal error check.
• No cross-repo impact in cloud/ — the cloud repo has its own hardcoded pgoptions.Log("INFO", true) which is pre-existing and out of scope.

---

If you push additional changes and want a new review, tag @shellhub-io/admin and a team member can trigger it.