Add unit tests for startEnvironment() readiness polling and retry logic

[Copilot]

The startEnvironment() function gained bounded readiness polling and a recovery landoStart() retry pass, but had no test coverage for those branches — leaving success/retry/failure paths unverified and prone to silent regression.

Changes

• Mock dev-environment-lando – added jest.mock for the lando module and imports for isEnvUp, landoStart, landoRebuild, getProxyContainer, landoInfo so each test can control readiness behavior independently.
• Three new startEnvironment test cases under a readiness polling and retry describe block:
  • Success on first check – isEnvUp returns true immediately; asserts no retry landoStart is issued.
  • Success after retry – isEnvUp exhausts all 6 first-pass attempts, then resolves on the second pass; asserts landoStart retry fires exactly once and isEnvUp is called 7 times total.
  • Total failure – isEnvUp always returns false; asserts both passes exhaust all 12 attempts and a UserError is thrown.
• Fake timers – tests that exercise the full polling loop use jest.useFakeTimers() + jest.runAllTimersAsync() to avoid real 2-second sleep delays. The failure-case rejection handler is registered before runAllTimersAsync() to prevent spurious unhandled-rejection failures.
• Scoped fs.readFileSync mock – intercepts only the instance_data.json path to avoid corrupting lazy module loads (e.g. chalk) during test execution.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud