fix(scripts): follow the 2-networking-a-fedramp directory rename

[scottonix]

Description

#162 (7033b8c) renamed fast/stages-aw/2-networking-a-fedramp-high to 2-networking-a-fedramp, and #173 (f64ce6c) updated the READMEs, but the four operator scripts still cd into the old path:

• scripts/deploy.sh:1066 — the FedRAMP High/Moderate option of stage 2 fails at cd ... || exit before deploy_networking runs;
• scripts/destroy.sh:665 and :1923;
• scripts/restore.sh:50;
• scripts/clean.sh:149.

This replaces the five occurrences with the current directory name. No other change.

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)
• Documentation update

Deployment & Compliance Impact

• Applicable Regimes:
  • US Region Restricted (e.g., Access Policy constraint)
  • FedRAMP Moderate
  • FedRAMP High
  • DoD IL4
  • DoD IL5
  • General / All
• NIST 800-53r5 Controls: none affected.

Checklist

Code Quality & Reusability

• My code adheres to the Maximize Reusability principle. I have not redefined common elements and have reused existing base configurations and modules where possible.
• I have checked that no existing module or configuration in modules/ or fast/ can be leveraged for this change.
• My code follows the established naming conventions outlined in documentation/naming-convention.md.

Documentation

• I have updated the README.md of the modified module or blueprint. (Not applicable — no documentation references the old path any more.)
• I have added/updated documentation for inputs (variables) and outputs. (Not applicable.)

Security

• My change adheres to GCP security best practices and the principle of least privilege.
• I have ensured compliance with the targeted regime (FedRAMP Moderate, FedRAMP High, IL5, etc.).

Testing

• I have tested my changes locally.
• I have included details of my testing in this PR.

Testing Performed

• bash -n on all four scripts: OK.
• shellcheck -S error on all four scripts: no findings before or after the change.
• grep -rn 2-networking-a-fedramp-high scripts/ returns nothing after the change; fast/stages-aw/2-networking-a-fedramp is the only FedRAMP networking directory in the tree.