docs(tests): npm/PowerShell wrappers, remove legacy shells (#562 4/4)

[WilliamBerryiii]

Pull Request

IMPORTANT: Before submitting, please remove all sensitive data, secrets, tokens, or confidential information. Ensure you've redacted any NDA-covered information, IP addresses, resource names, or security-related details that shouldn't be publicly disclosed.

Description

Final PR (4 of 4) in the static Go contract-test rollout stack for #562. Replaces the legacy run-contract-tests.sh / run-deployment-tests.sh Bash wrappers with the npm + PowerShell entry points landed in #571 and #572, and updates every doc that referenced the old scripts so contributors land on the supported workflow.

Removal of the two shell wrappers is a breaking change for anyone invoking them directly. The replacement is npm run go-test (contract) and npm run go-test:deploy:terraform|bicep / npm run go-test:deploy (deployment).

Related Issue

Closes #570
Relates to #562

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Blueprint modification or addition
• Component modification or addition
• Documentation update
• CI/CD pipeline change
• Other (please describe):

Implementation Details

Blueprint docs

• blueprints/full-single-node-cluster/README.md — Testing section now lists "npm Entry Points" instead of "Helper Scripts"; the "When modifying this blueprint" workflow uses npm run go-test for contract baselines and npm run go-test:deploy:<framework> for deployments.
• blueprints/full-single-node-cluster/tests/README.md — Quick Start, Setup, Running Contract Tests, Running Deployment Tests, Automation Entry Points, and the end-to-end example all use npm scripts; jq (only needed by the shell wrappers) is dropped from recommended dependencies; deployment env-var section now lists ARM_SUBSCRIPTION_ID, CUSTOM_LOCATIONS_OID, and ADMIN_PASSWORD as required rather than auto-detected.

Test code comments

• blueprints/full-single-node-cluster/tests/deploy_bicep_test.go and deploy_terraform_test.go — strip (set in run-deployment-tests.sh) comments now that env vars are set directly by the caller (npm script, PowerShell wrapper, or developer shell).

Removed wrappers

• blueprints/full-single-node-cluster/tests/run-contract-tests.sh — superseded by npm run go-test.
• blueprints/full-single-node-cluster/tests/run-deployment-tests.sh — superseded by npm run go-test:deploy:terraform|bicep (and npm run go-test:deploy for both).

Repo-wide docs

• docs/contributing/testing-validation.md — Contract/Deployment test instructions and the example blueprints/{name}/tests/ layout drop the .sh wrappers and use npm scripts; the new-blueprint checklist asks authors to add "package scripts" rather than helper scripts.
• docs/getting-started/blueprint-developer.md — blueprint test-author checklist and Running Tests snippets point at npm run go-test and npm run go-test:deploy:terraform.

Testing Performed

• Terraform plan/apply
• Blueprint deployment test
• Unit tests
• Integration tests
• Bug fix includes regression test (see Test Policy)
• Manual validation
• Other: repo-wide grep confirms zero remaining references to the deleted wrappers outside .copilot-tracking/.

Validation Steps

• grep -rn "run-contract-tests\.sh\|run-deployment-tests\.sh" outside .copilot-tracking/ returns zero references after this PR.
• npm run mdlint-fix — no changes required.
• npm run lint (composite of mdlint, cspell, yaml, format-json, docker-lint) — exit 0; only pre-existing baseline warnings unrelated to this stack.

Checklist

• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have run terraform fmt on all Terraform code
• I have run terraform validate on all Terraform code
• I have run az bicep format on all Bicep code
• I have run az bicep build to validate all Bicep code
• I have checked for any sensitive data/tokens that should not be committed
• Lint checks pass (run applicable linters for changed file types)

Security Review

• No credentials, secrets, or tokens are hardcoded or logged
• RBAC and identity changes follow least-privilege principles
• No new network exposure or public endpoints introduced without justification
• Dependency additions or updates have been reviewed for known vulnerabilities
• Container image changes use pinned digests or SHA references

This PR does not touch SECURITY.md, src/000-cloud/010-security-identity/, or deploy/.

Additional Notes

Stacked on top of #571 (foundation), #572 (detector + PowerShell wrapper), and #573 (CI wiring).

Screenshots (if applicable)

N/A.

🔒 - Generated by Copilot

[rezatnoMsirhC]

The "Environment Variables Reference" section contains an "Auto-Detected Variables" subsection header and lists ARM_SUBSCRIPTION_ID and CUSTOM_LOCATIONS_OID with a fallback of "Script fails if not detected". The shell scripts that performed this auto-detection (run-deployment-tests.sh) are removed in this PR, and the npm deployment scripts (go-test:deploy:*) call go test directly without any env-var detection. This directly contradicts the updated Setup section added by this PR ("Set ARM_SUBSCRIPTION_ID before running deployment tests").

Consider renaming the subsection from "Auto-Detected Variables" to "Required Variables" and updating the Fallback column to reflect that these must now be set manually.

[rezatnoMsirhC]

The "Key Differences: Terraform vs Bicep Tests" table has two cells that still reference the deleted shell scripts: (+) Required (auto-generated by script) for ADMIN_PASSWORD and (+) Required (auto-detected by script) for Custom Locations OID. With run-deployment-tests.sh removed, neither the npm scripts nor the Go tests auto-generate or auto-detect these values.

Suggested update:

• ADMIN_PASSWORD: (+) Required (set via ADMIN_PASSWORD env var)
• CUSTOM_LOCATIONS_OID: (+) Required (set via CUSTOM_LOCATIONS_OID env var)

[rezatnoMsirhC]

Step 6 was changed from a concrete instruction ("Copy and adapt run-contract-tests.sh and run-deployment-tests.sh from the reference implementation") to the vaguer "Add package scripts that run the Go contract and deployment tests for the blueprint." A new blueprint author has no pointer to what scripts to add or how to structure them.

Consider adding a reference to the existing pattern, for example: "Add package scripts (following the go-test:* pattern in package.json) that run the Go contract and deployment tests for the blueprint."