[eas-cli] Bump Node to 20.18.3

[ramonclaudio]

Why

We recently updated @expo/env with a new shared API for setting NODE_ENV consistently to either development or production. Unfortunately, we can't use that version in EAS CLI yet because @expo/env uses util.parseEnv(), which Node didn't add until 20.12.0.

How

I bumped EAS CLI to 20.18.3, which matches the oldest EAS Build images that currently use Node 20. I went with ^20.18.3 || >=22.0.0 because using >=20.18.3 would also include Node 21.0.0 through 21.6.x (which don't include the util.parseEnv() API). I also updated the test workflow and CLAUDE.md to reflect the changes.

Test Plan

All tests pass.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.05%. Comparing base (66dbcaf) to head (ab3e00d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4279   +/-   ##
=======================================
  Coverage   64.05%   64.05%           
=======================================
  Files        1042     1042           
  Lines       48009    48009           
  Branches    10130    10130           
=======================================
  Hits        30745    30745           
  Misses      17148    17148           
  Partials      116      116           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

✅ Thank you for adding the changelog entry!

[github-actions]

Subscribed to pull request

File Patterns	Mentions
packages/eas-cli/**	@douglowder

Generated by CodeMention

Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead.