Fix 2 issues with VMWare SDK and included nspkg.pth files

[cigamit]

This resolves 2 issues.

1. The VMWare SDK was failing to load as it still required pkg_resources, which was removed in later versions of setuptools. So we pin to an earlier version until this is resolves
2. The additional nspkg.pth files that are automatically being added were causing pip to fail to install packages during job runs. So cleaning these up as they are unneeded. Resolves Legacy namespace-package .pth files in ascender-ee break all pip source builds ascender#767

[ciq-it-service-account]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Copilot]

🟡 Changes recommended

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR adjusts the execution environment build to address VMware SDK runtime compatibility with newer setuptools and to prevent legacy namespace .pth shims from breaking pip source builds in derived images.

Changes:

• Pin setuptools<81 to keep pkg_resources available for the vSphere Automation SDK runtime imports.
• Remove legacy NSX SDK *-nspkg.pth files from site-packages during the final image build to restore pip isolated build behavior.

File summaries

File	Description
execution-environment.yml	Pins setuptools to preserve VMware SDK compatibility and adds a build-step cleanup of NSX namespace-package .pth shims.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.