feature!: add support for eas cli installs

[byCedric]

BREAKING CHANGE: Github Action inputs are changed to allow both Expo and EAS CLI.

Part of #97

[jonsamp]

I'm not familiar enough with the code to give you code-level review, but I tried this out in a project of mine and it worked well!

Here's my action for reference:

name: update
on:
  push:
    branches: [main]

jobs:
  update:
    name: Install and update
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v1
        with:
          node-version: 15.x
      - uses: expo/expo-github-action@eas-support
        with:
          expo-version: latest
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}
          expo-cache: true
          eas-cache: true
      - name: Find cache
        id: yarn-cache-dir-path
        run: echo "::set-output name=dir::$(yarn cache dir)"
      - name: Restore cache
        uses: actions/cache@v2
        with:
          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
          restore-keys: |
            ${{ runner.os }}-yarn-
      - run: yarn install
      - run: eas branch:publish $(echo ${{ github.ref }} | sed 's_refs/heads/__') --message "${{ github.event.head_commit.message }}"

[byCedric]

Nice, thanks for testing it! We should probably add some output helpers to get you of that ugly echo ${{ github.ref }} | sed 's_refs/heads/__'. That would probably be a follow-up thing.

Also, random sidenote, I would stick with the even-numbered node versions. The uneven are more like experiments and will be EOL soon see releases