job list: Config column has always rendered empty — renderer reads an invented 'configId' key

[padak]

Found while fixing the same bug in the web UI (PR #658): the Queue API job row carries the config id under the key config (service passes rows through verbatim — JobService._fetch_project_jobs only adds project_alias; the repo's own realistic fixture JOB_DETAIL_RESPONSE in tests/test_cli.py:3236 says "config": "123").

But output.py:411 renders the CLI's job list Config column as str(job.get("configId", job.get("config_id", ""))) — neither key exists on the real payload, so kbagent job list has always printed an empty Config column.

The bug survived because the fixtures in tests/test_output.py and tests/test_services.py hand-write "configId", asserting against the same invented key the renderer reads — the tests were never checking anything real. Fix must correct BOTH the renderer (read config, keep config_id fallback for any older payloads) and the fixtures (use the real Queue API field name), otherwise the fix would pass the existing tests without proving anything.

Web UI side is already fixed in PR #658 (types.ts configId → config: string | null).

[padak]

Fixed in #662 (commit da4fb98).

output.py now renders the Config column from the real Queue API key with a legacy fallback:

str(job.get("config", job.get("configId", "")))

Both halves of the fix landed as this issue required: the renderer reads config first, and the hand-written "configId" fixtures in tests/test_output.py were replaced with the real field name, so the tests now assert against a payload shape that actually exists. tests/test_output.py:266 carries a comment recording why (the old fixtures were asserting the same invented key the renderer read).

The web UI twin was fixed separately in #658.