Implement eas env commands

[khamilowicz]

Why

Implements the following commands:

• eas env:create ENG-11913
• eas env:get ENG-11915
• eas env:delete ENG-11914
• eas env:list ENG-11917
• eas env:update ENG-11918 (Currently only delegates to env:create)

Also, as discussed on Linear, implements eas env:shared:create/update/get/delete/link/unlink as --scope shared flag on mentioned commands. (ENG-11927, ENG-11926, ENG-11925, ENG-11921, ENG-11922, ENG-11923).

How

Created commands and mutations using updated backend (https://github.com/expo/universe/pull/15153).

Deployment

1. https://github.com/expo/universe/pull/15153
2. Implement eas env commands #2350

Test Plan

Each command accepts arguments both in interactive mode (user is prompted for input) and non-interactive (arguments are passed inline).

The following flow will create both project and shared variables, then it will link and unlink shared variable from the project, and finally delete both of them. Commands are executed both with inline arguments and prompts.
From an existing app directory:

1. Create project variable interactively - eas env:create and provide name, value and select environment
2. Create shared variable non-interactively - env:create --scope SHARED --name sharedVariable --value someValue
3. eas env:list and select environment - displays only project var
4. eas env:list --format long --scope SHARED - displays only shared var in long format
5. eas env:link - select shared var and environment
6. eas env:list - shared variable should be added to selected env
7. eas env:unlink --environment SELECTEDENV --name sharedVariable
8. eas env:list - shared variable should be removed
9. eas env:delete - delete project variable
10. eas env:delete --scope SHARED - delete shared environment

[linear]

ENG-11913 Add `eas env:create` command

[github-actions]

❌ It looks like a changelog entry is missing for this PR. You have two options: you can add it manually, or you can use the changelog bot to do it for you.
🤖 To use the bot, simply comment on this PR with the command /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message].
⏩ If this PR doesn't require a changelog entry, such as if it's an internal change that doesn't affect the user experience, you can add the "no changelog" label to the PR.