docs(changelog): 0.58.0 — upgrade on pnpm installs the newest release

[leemour]

Why

On pnpm 11, the default minimumReleaseAge (one day) made max upgrade install the previous version. The owner hit it: max upgrade left 0.56.0 after 0.57.0 was out. cli-base 0.40.2 (WireCatLabs/cli-base#181) fixes it by running pnpm add -g @wirecat/max-cli@latest --config.minimumReleaseAgeExclude=@wirecat/*.

What

The dependency work was already done: #702 pinned @wirecat/cli-base 0.40.2 directly in package.json and updated both installer-argv assertions in src/commands/upgrade.test.ts. The published @wirecat/max-cli@0.58.0 ships with cli-base 0.40.2.

The 0.58.0 notes never mentioned the fix, so this PR adds one bullet under ### Исправлено in ## 0.58.0. It does not go under «Не выпущено», because that would make the next release announce a fix users already have. To update the GitHub release text after merge, run bin/sync-release-notes 0.58.0.

Testing

pnpm lint and pnpm docs:check pass. The diff only touches Markdown, so I did not run typecheck, parity or the test matrix locally. CI runs them.

🤖 Generated with Claude Code

[leemour]

Held: the changelog guard refuses edits to the released 0.58.0 section, and the cli-base 0.40.2 fix already shipped in 0.58.0 (#702). Putting it under «Не выпущено» would make the next release announce a fix users already have. Waiting for a decision: close this PR, or move the line under «Не выпущено».

[leemour]

Not needed: cli-base 0.40.2 and its test updates came in with #702 and shipped in 0.58.0. The changelog guard refuses edits to a released section.