Clarify rollForward: disable guidance for lock-file workflows in global.json docs

[Copilot]

The global.json article didn’t surface an important recommendation: when you use dependency lock files, you should also pin SDK selection with rollForward: disable to keep toolchain resolution deterministic. This update adds that guidance directly where rollForward values are defined.

• Docs update (rollForward policy table)

  • Updated the disable row in docs/core/tools/global-json.md to explicitly recommend disable for lock-file scenarios.
  • Kept the change scoped to the existing behavior table to improve discoverability at decision time.

• Resulting guidance

  {
    "sdk": {
      "version": "8.0.302",
      "rollForward": "disable"
    }
  }

  disable now explicitly communicates: exact SDK match, and recommended use with lock files so SDK version and dependency graph remain in lockstep.

---

Internal previews

📄 File	🔗 Preview link
docs/core/tools/global-json.md	global.json overview

[Copilot]

Pull request overview

Updates the global.json documentation to make SDK selection more deterministic when using lock-file-based dependency workflows, by recommending rollForward: disable directly in the rollForward behavior table.

Changes:

• Refines the disable roll-forward policy description to emphasize exact SDK matching.
• Adds a footnote recommending rollForward: disable when using lock files, with references to related GitHub issues.