OpenBolt 5.x docs: follow-ups to #537 #548

#537 left a few OpenBolt pages as they were, on the grounds that they were old but harmless. Checking them against OpenBolt 5.6.0 showed that several tell readers to do things that fail. This issue tracks the fixes.

• Host OpenBolt's JSON schemas on the docs site #549 VS Code schemas: host OpenBolt's own JSON schemas on the docs site and point vscode_and_bolt.md at them. The Forge schemas are Puppet Bolt's: they still describe pcp and lack choria. Closes [OpenBolt] Schema files are linked to puppet forge #353.

• Update the OpenBolt getting started guide for current Docker #550 Getting started: replace the 2018 amd64-only target image, move to docker compose, and drop the pointer to puppetlabs/bolt-getting-started.

• Update the stale OpenBolt pages left out of the #537 work #551 Stale pages: cut developer_updates.md down to the dotted fact names section that openbolt main links to. Rename Bolt to OpenBolt in experimental_features.md and drop its "introduced in" notes, remove the "introduced in Bolt 2.x" callouts elsewhere, and correct the version 1 inventory claim.

• Verify the OpenBolt Windows guide and remove the TIG stack guide #552 Windows guide: verify automating_windows_targets.md against Windows 11 and fix:

  • the WinRM and execution policy prerequisites
  • the example package, since Frogsay no longer installs
  • the PowerShell module signing claim in troubleshooting.md

  Also remove the TIG stack guide, which needs CentOS 7 and an InfluxDB module from 2019 that requires Puppet older than 6.

Each change is verified against packaged OpenBolt 5.6.0.

Assisted by Claude.