[Feature]: Expose all env variables via a `:config-*` command

[tusharmath]

1. Why Do You NEED This Feature?

Some of the configurations are only possible to edit via env variables this affects discoverability and the ability to update them. Having a :config-* command will make this a lot easier.

2. What Is NOT Possible Right Now?

There is no option to discover newly created configurations.

3. What WILL Be Possible With This Feature?

I will be able to tune ForgeCode for my usecase without explicitly setting env variables.

Proposed Solution (User Experience)

We will have two sets of commands on ZSH

:config-retry-initial-backoff

This will persist the configuration in .config.json

and

:retry-initial-backoff

Will set the config only for that session.

Alternatives Considered

No response

Feature Category

Configuration

Priority/Impact

High - Would significantly improve my workflow

Examples from Other Tools

No response

Additional Context

No response

Pre-submission Checklist

• I have searched existing issues and confirmed this is not a duplicate
• I am willing to submit a PR to implement this feature

[chengyixu]

/attempt

I'd like to work on this. I'll implement the :config-* command system that:

1. Adds a :config-<setting> command pattern that persists values to .config.json
2. Adds a :<setting> command pattern for session-only configuration
3. Discovers and exposes all env-variable-based configurations through these commands
4. Ensures backward compatibility with existing env variable configuration

I'm familiar with ForgeCode's architecture and can have a PR ready within 48 hours.

[zhaog100]

/attempt

[trasnake87]

/attempt

[marchantdev]

/attempt #2638

PR submitted: #2682

Implements forge config get env (lists all 38 FORGE_* vars with defaults), forge config set env KEY VALUE (writes to .env + applies immediately), and a ZSH :config-env / :ce fzf picker. No restart needed after setting a variable.