Preserve Magpie upstream model groups and native Hermes configuration controls #1092

Magpie-backed DSH, Hermes and Grok sessions do not consistently show their
dynamic upstream model groups. Hermes compatibility selectors can also replace
an agent's newer native model and reasoning controls.

Baseline: e3171d69 (Codeg 0.42.0).

Representative advertised values:

magpie/auto/fast
custom:magpie:opencode-go/vendor/model:1
["magpie","auto/fast"]
["magpie-responses","openai/reasoner"]
["magpie-anthropic","anthropic/claude"]

The last three values are opaque DSH selectors. Their original strings must
reach ACP unchanged, and the protocol routes must remain distinct.

Expected:

• Derive source labels from the IDs inside these known wrappers, without
  maintaining a provider/model table in Codeg.
• Preserve meaningful native groups, descriptions, order within groups,
  original selector strings and legitimate slashes in display names.
• Prefer native Hermes model/config options on establishment, pushes and setter
  responses. Keep the legacy fallback for older Hermes, and handle native
  controls first arriving in a later update.
• Show the advertised legacy permission control when native model/thought
  options do not supersede it. Native and legacy permission state must agree,
  so the CLI cannot skip an explicitly requested restrictive mode.
• Show only reasoning choices actually advertised by the agent and refresh
  them when the model changes.

Related: #776 and #777. Native Hermes metadata/control support and Magpie
catalog export are being implemented in their owning projects. This Codeg
change is limited to display compatibility and native-option ownership.