Backfill v1.0.1 public source and release metadata

[Alexander Zaslonov (azaslonov)]

Summary

Backfill the missing public v1.0.1 source release from the historical upstream point 420b993, without including newer v1.0.2 changes. This PR intentionally targets the historical release/v1.0.1 branch, not main.

• Align package.json and both package-lock.json version fields to 1.0.1.
• Add historical release notes covering multi-environment publishing, filtered-publish parity, gateway reconciliation, revision handling, SOAP round trips, concurrency fixes, and dependency updates.
• Port release-time fixes: reject an explicitly empty environment.appliesTo before planning deletes, and classify DELETE failures using HTTP status and structured error codes instead of message text.
• Include regression tests for 404, HTTP 412, PreconditionFailed, validation errors, and empty environment scopes.
• Public-only ancestry and an eight-file change allowlist were verified. No internal pipeline configuration or commits were imported.

Validation

• All runtime source files match the corresponding release build source after line-ending/trailing-whitespace normalization.
• Both package manifests match the release build manifests exactly; no dependency changes.
• 150 focused tests passed across three files.
• Build and lint passed.
• Constitution-focused code review: no Blocker or Required findings; the suggested DELETE tests were verified to already exist and pass.
• Whitespace checks passed. No new full suite or live Azure integration run was performed for this backfill.

Related Issues

Release source alignment only; no new issue closure is claimed.

Release Sequence

After review, merge only into release/v1.0.1. Verify version 1.0.1 on the resulting historical release commit before creating an annotated v1.0.1 tag and publishing the GitHub release. Do not tag current main as v1.0.1: it already contains newer changes. The main-only Squad Release workflow does not run on this historical branch, so this backfill needs an explicit GitHub tag/release step. Do not start another npm/ESRP publication.