Decouple package publishing and document releases

[magiccodingman]

What changed

• switch npm publishing to Trusted Publishing with GitHub OIDC, Node 24, and no long-lived npm token
• limit automatic npm publishing to client/src/**, package metadata, and the client build script
• split the shared NuGet version into independent versions for Snapshot.Protocol, Snapshot.Processing, Snapshot.Playwright, and Snapshot.Cli
• require package-specific version bumps when a corresponding source project changes
• keep full restore/test/pack validation while publishing only NuGet package versions that do not already exist
• remove README, license, and logo changes from automatic NuGet publishing triggers
• document the recommended minified jsDelivr @latest URL, exact-version pinning, and the readable debug build
• document the current .NET 10 requirement and point to Directory.Build.props, global.json, and project files as authoritative sources
• expand release documentation with the exact npm and NuGet trusted-publishing configuration and independent version properties

Why

Documentation and artwork edits should not manufacture package releases, and changing one .NET library should not force unrelated packages to receive synchronized versions. Package versions now act as explicit release switches while the workflow still validates the complete dependency set.

The existing canonical validation, conservative processing/minification, and safe fallback documentation was already comprehensive, so this PR preserves it and links the new installation and release guidance into the existing docs instead of duplicating those sections.

Validation

• parsed all modified workflow files as YAML
• parsed eng/Versions.props and all modified project files as XML
• verified the branch diff contains no NPM_ACCESS_TOKEN or shared SnapshotPackageVersion references
• repository CI is running the full cross-platform .NET build, tests, package validation, and browser end-to-end suite