fix(envutil): route GetIntFromEnv warnings through logger when provided

[Copilot]

GetIntFromEnv accepted a *logger.Logger but only used it for success messages — warnings for invalid/out-of-bounds values always went directly to os.Stderr, making the logger parameter misleading and preventing callers from controlling warning output.

Changes

• pkg/envutil/envutil.go: Introduced a local warn closure that routes through log.Printf when a logger is provided, falling back to fmt.Fprintln(os.Stderr, ...) only when log is nil

warn := func(msg string) {
    if log != nil {
        log.Printf("WARNING: %s", msg)
    } else {
        fmt.Fprintln(os.Stderr, console.FormatWarningMessage(msg))
    }
}

No behavior change for callers passing nil as the logger.

[Copilot]

Pull request overview

Updates GetIntFromEnv to route warning output through the provided *logger.Logger (instead of always writing directly to os.Stderr), aiming to make the log parameter reflect actual warning behavior.

Changes:

• Added a local warn helper in GetIntFromEnv to centralize warning emission and choose between logger vs. direct stderr output.
• Updated parse/out-of-bounds branches to call the shared warn helper.
• Updated the function comment to reflect logger-based warning routing.

Show a summary per file

File	Description
pkg/envutil/envutil.go	Centralizes warning emission and routes warnings via logger when provided.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 1