[ENG-1242][eas-cli] copy Expo Classic credentials to EAS if user is eligible

[quinlanj]

Checklist

• I've added an entry to CHANGELOG.md if necessary.
• I've tagged the changelog entry with [EAS BUILD API] if it's a part of a breaking change to EAS Build API (only possible when updating @expo/eas-build-job package).

Why

• If the user hasn't set up any credentials in EAS but has credentials in Expo Classic (expo-cli), copy them over. We will give users this option if they are running eas build:android or using the beta credentials manager.
• This change will allow us to disregard Expo Classic (expo-cli) credentials in the future and simplify logic because if a user is no longer eligible for a 'copy', we can assume that the legacy credentials were already copied, or the user has chosen to create their EAS credentials from scratch.

User Experience

• User will be prompted to copy over their Expo Classic credentials
• If they say no, and go on to create credentials in the EAS system, they will no longer be prompted on future builds because they are no longer eligible to have their Expo Classic credentials copied
• If they say yes, all credentials from Expo Classic will be copied to the EAS system

Test Plan

• new tests pass
• manual sanity checks

[linear]

ENG-1242 copy over expo-cli android credentials to eas-cli

[github-actions]

Size Change: +2.22 kB (0%)

Total Size: 37.5 MB

Filename	Size	Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz	37.5 MB	+2.22 kB (0%)

_{compressed-size-action}

[FiberJW]