ci: run docs build+deploy inside dev workflow

[PTKu]

Summary

• Move docs build + Pages deploy into dev.yml as jobs chained via needs: build → needs: docs.
• docs.yml kept as manual-only (workflow_dispatch) fallback; auto trigger removed.
• No actions/checkout in the new docs job — reuses the self-hosted runner workspace produced by build, so restored NuGet packages and compiled outputs are available to docfx metadata.

Why

Previous standalone docs run failed (run 24445347613) with CS0246 across AXSharp / Serilog / Microsoft.Extensions / Blazorise types — docfx metadata ran without prior restore/build. Keeping docs in the same workflow guarantees artifacts exist on the runner when docfx runs.

Caveats

• Assumes the [self-hosted, Windows, X64, L2, AX] label resolves to a single runner (or that needs: consistently lands on the same agent). If the pool grows, switch to artifact upload/download or pin a runner label.
• Added pages: write and id-token: write permissions at workflow level for deploy.

Test plan

• workflow_dispatch on dev runs build → docs → deploy successfully
• Pages site updates after a successful dev run
• Manual docs workflow still dispatchable