Deprecated dependencies when installing `eas-cli@latest`

### Build/Submit details page URL

_No response_

### Summary

When installing the latest version of `eas-cli` globally using Yarn, I see multiple deprecation and unsupported package warnings. It still installs successfully, but the warnings suggest that dependencies are outdated or unsupported.

### Managed or bare?

Bare

### Environment

expo-env-info 2.0.7 environment info:
System:
OS: Linux 6.16 Fedora Linux 42 (Workstation Edition)
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 22.19.0 - ~/.nvm/versions/node/v22.19.0/bin/node
Yarn: 1.22.22 - /usr/bin/yarn
npm: 11.6.0 - ~/.nvm/versions/node/v22.19.0/bin/npm
SDKs:
Android SDK:
API Levels: 36
Build Tools: 36.0.0, 36.1.0
System Images: android-36 | Google Play Intel x86_64 Atom
npmPackages:
expo: ~53.0.22 => 53.0.22
react: 19.0.0 => 19.0.0
react-native: 0.79.5 => 0.79.5
Expo Workflow: bare

### Error output

* `xmldom@0.7.13: this version is no longer supported`
* `lodash.get@4.4.2: This package is deprecated. Use optional chaining (?.) instead.`
* `@oclif/screen@3.0.8: Package no longer supported`
* `sudo-prompt@9.1.1: Package no longer supported`
* `rimraf@2.4.5: versions prior to v4 are no longer supported`
* `glob@6.0.4: versions prior to v9 are no longer supported`
* `inflight@1.0.6: This module is not supported and leaks memory`
* `ts-node@10.9.2` has unmet peer dependency `@types/node@*`
* `ts-node@10.9.2` has unmet peer dependency `typescript@>=2.7`

### Reproducible demo or steps to reproduce from a blank project

1. Run:
```bash
yarn global add eas-cli@latest
```

2. Observe warnings in the terminal.