eas-cli should provide instructions / alternative to "Authentication with Apple Developer Portal failed!"

### Build/Submit details page URL

_No response_

### Summary

Today it's the first time I have issues building with EAS, generally I build for production and then I do an auto-submit.

This time it didn't work, potentially due to apple's own problems ([related to #2143](https://github.com/expo/eas-cli/issues/2143)) with rate limit or perhaps it's related to the fact i have moved between a few different countries in the last days and it triggered some sort of flag on their security policies ( logging via browser works, it's just the eas build that's not working ).

Regardless of the reason, i believe `eas-cli` should point the user to an alternative way of building and/or submiting the build since not being able to submit a bugfix could potentially be catastrophic.

>✖ Logging in...
Authentication with Apple Developer Portal failed!
Too many verification codes have been sent. Enter the last code you received or try again later.
Error: build command failed.

### Managed or bare?

managed

### Environment

expo-env-info 1.2.2 environment info:
System:
OS: macOS 14.4
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.6.0 - /opt/homebrew/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.9.2 - /opt/homebrew/bin/npm
Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12700392
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
expo: ^52.0.37 => 52.0.37
expo-router: ~4.0.17 => 4.0.17
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
react-native: 0.76.7 => 0.76.7
react-native-web: ~0.19.13 => 0.19.13
npmGlobalPackages:
eas-cli: 14.1.0
Expo Workflow: bare

---

Running 15 checks on your project...
14/15 checks passed. 1 checks failed. Possible issues detected:
Use the --verbose flag to see more details about passed checks.

Advice:
- Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

### Error output

_No response_

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

not really a project related problem