Fix project telemetry and API documentation ingestion

[PrzemyslawKlys]

What changed

• correct GitHub project telemetry so open issue counts exclude pull requests
• allow project API generation from XML documentation without requiring a matching assembly
• merge multiple XML documentation assemblies into one project API reference
• hydrate missing PowerShell API help from an exact published PowerShell Gallery package version
• keep checked-out or explicit artifacts authoritative and never forward the GitHub artifact token to PowerShell Gallery
• preserve freshness, placeholder, and source checks across every API input
• add regression coverage for issue pagination, multi-assembly APIs, exact package selection, token isolation, and local-source precedence

Why

Project hubs were displaying GitHub's combined issue-and-pull-request count as open issues. Multi-package projects such as ChartForgeX need one coherent API surface rather than silently documenting only the first assembly. Clean website runners also cannot rely on ignored WebsiteArtifacts folders, so PowerShell help now falls back to the exact public package already recorded in the catalog.

The clean Website integration generated all seven configured API projects from tracked source or public packages, including 663 ChartForgeX types from six XML inputs.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.