fix(configurator): bounded native VPN and Git advice

[lweberru]

Summary

• Reuse the existing reviewed-metadata field-overview path for native VPN and DevOps Git information; preserve semantic classification, separate protected bindings, and all execution gates.
• Make informational default/prerequisite intent explicit and keep general advice compact inside the unchanged response/context budgets.
• Strengthen VPN native field/default/PSK and DevOps field criteria, with negative and one-request deterministic regressions; regenerate source-bound knowledge/catalogue.

Verification

• Pinned Node 24.21.0/npm 11.19.0: npm run check passed (815 unit tests; 66 environment-dependent skips).
• Current-source real-model repetitions: VPN 3/3, DevOps 3/3, Governance 2/2; all reviewed, no questions/changes, 1493/975/1481 characters respectively (asserted <=2400).
• Knowledge: 40c40462421ad8f292a21871ce9a82396c1300239c400de0f6de22e5d2bcef93; factual suite: eff58501eae3dd3bdff61f858e9bb3d09fb5182fa3f5bc40de43aa360d1dfe91.
• Failed earlier model repetitions and release 38974014187 remain failures with preserved receipts; no unchanged-source qualification retry or weakened oracle.

Delivery

Follow-up to #109–#111: a fresh manual Development release must pass the complete repeated model suite, dialogue, build/browser and protected deployment gates before activation. No production deployment or customer Apply.