fix(misc): mark migration for escaping env vars as skipped in nx repair

[AgentEnder]

Current Behavior

The migration to escape env vars is ran any time someone runs nx repair

Expected Behavior

New workspaces may have env vars that were written with expansion in mind, so running nx repair shouldn't escape them

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Apr 19, 2024 4:40pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a28572b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=75234ae1b5685cfb084ff553922c287d2b8e32bb --head=a28572b0ccac7a921bfe72417aadd22e41b4da53 --parallel=1
• nx affected --targets=lint,test,build --base=75234ae1b5685cfb084ff553922c287d2b8e32bb --head=a28572b0ccac7a921bfe72417aadd22e41b4da53 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=75234ae1b5685cfb084ff553922c287d2b8e32bb --head=a28572b0ccac7a921bfe72417aadd22e41b4da53
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=75234ae1b5685cfb084ff553922c287d2b8e32bb --head=a28572b0ccac7a921bfe72417aadd22e41b4da53

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.