The Github Pages deployment of elements should be migrated to Foundations

[willmcvay]

• Currently the elements project is being deployed from the old elements repo to Github Pages. This should be migrated across to Foundations and the old repo archived.
• This should be part of the release:prod workflow if Elements is manually released to prod and has changed see There should be a release:prod workflow #119

[trankhacvy]

Hey @willmcvay, this is my solution for this issue but I'm not sure it's good way. Could you please review it and give your comment ?

In release-production.yml, we add:

  deploy_story_book:
    runs-on: ubuntu-latest
    needs: setup
    steps:
      - name: checks out repository to $GITHUB_WORKSPACE
        uses: actions/checkout@v1

      - name: Setup Node Environement
        uses: actions/setup-node@v1
        with:
          node-version: 12

      - name: Get installed node_modules
        id: cache
        uses: actions/cache@v1
        with:
          path: node_modules
          key: build-${{ hashFiles('**/yarn.lock') }}
          restore-keys: |
            build-${{ hashFiles('**/yarn.lock') }}
      - name: build story book
        run: yarn build-storybook

      - name: deploy story book to GH pages
        uses: JamesIves/github-pages-deploy-action@releases/v3
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          BASE_BRANCH: master # The branch the action should deploy from.
          BRANCH: gh-pages # The branch the action should deploy to.
          FOLDER: out # The folder the action should deploy.

And then in root package.json and package.json of elements package we add
"build-storybook": "build-storybook -o out"
script to build storybook.