Refine docs command configuration and error handling

[Jared Holgate (jaredfholgate)]

Summary

Follow-up to #20183 that incorporates Anthony's post-merge feedback and the useful parts of the closed reference #20223.

• remove documentation-specific pseudo-diagnostic codes and use the normal CLI exception path for setup, rendering, and write failures
• use the existing per-input diagnostic/SARIF flow used by other pattern-based commands
• consolidate the docs command group and generation handler in DocsGenerateCommand
• make bicepconfig.json the source of template file and include-root settings
• keep custom template values invocation-specific through CLI options and JSON-RPC request values
• remove documentation.template.values from configuration and reject it with an actionable error
• retain the explicit Microsoft.Extensions.FileSystemGlobbing dependency because Bicep.Core uses it directly
• preserve the released JSON-RPC response shape for compatibility

Behavior

--template-file and --template-root are removed. Templates are selected through documentation.template.file and documentation.template.includeRoot.

--custom-template-value and --custom-template-value-file-path remain repeatable and are applied in command-line order. JSON-RPC similarly accepts per-request custom values while resolving templates from bicepconfig.json.

Pattern compilation diagnostics continue to allow valid modules to render. Setup, template, filesystem, and write exceptions stop the command, matching existing CLI commands.

AVM tooling

Azure/azure-verified-modules-tools PR #101 updates the parity tooling to configure one dispatcher template through bicepconfig.json while keeping per-module values invocation-specific.

The final full validation used Azure/bicep-registry-modules commit 96a1dcb69b9bbb9c56638c4f5c457914d3e8bd21:

• 573 eligible modules evaluated
• 572 READMEs generated; all 572 matched byte-for-byte
• one retained compiler failure in avm/ptn/app/container-job-toolkit
• nine known parameter-model differences
• one upstream README/test-metadata example-name drift in avm/ptn/sa/conversation-knowledge-mining
• validation checkout configuration restored byte-for-byte with no tracked changes

Validation

• full Bicep.sln build: 0 warnings, 0 errors
• Bicep.Cli.IntegrationTests: 1,133 passed
• Bicep.Core.UnitTests: 7,202 passed
• Bicep.RpcClient.Tests: 95 passed, 1 skipped
• pull request CI passed across CLI builds, .NET tests, live/e2e tests, VS Code, Visual Studio, playground, and NuGet packaging

Microsoft Reviewers: Open in CodeFlow

[github-actions]

Test this change out locally with the following install scripts (Action run 34277737550)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 34277737550

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 34277737550"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 34277737550

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 34277737550"

[Anthony Martin (anthony-c-martin)]

Looks great, thank you!