Document JavaScript source map workflows

[ejsmith]

Summary

• explain how Exceptionless automatically discovers and caches publicly available JavaScript source maps
• document manual and CI/CD uploads using project-scoped source-maps:write tokens
• show the source-map upload API contract and where it fits in a deployment pipeline
• add verification, troubleshooting, security, storage, and retention guidance
• link the guide from the JavaScript client documentation

Impact

Users can choose between publishing source maps for automatic discovery or keeping them private and uploading them during deployment. The CI/CD guidance stays tool-agnostic so teams can integrate the upload into their existing build system without adopting a prescribed workflow.

This is documentation-only and does not change runtime behavior or public API contracts.

Validation

• cd docs && deno task verify
• documentation site build passed
• 4 documentation tests passed
• telemetry and internal link/anchor verification passed

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
Exceptionless.Core	73%	66%	9587	➖
Exceptionless.AppHost	38%	40%	139	❌
Exceptionless.Insulation	37%	35%	286	❌
Exceptionless.Web	84%	67%	6935	✔
Summary	77% (22857 / 29790)	66% (10503 / 16026)	16947	✔