Include the zipped extension in each release

Since #3421 added automatic releases, now we can also include the built extension for each release.

There are several actions that allow attaching files to releases, so we just need to ensure that they’re compatible with our workflow, e.g.

    - name: Update extension’s meta
      env:
        VER: ${{ needs.Version.outputs.version }}
      run: |
        echo https://github.com/$GITHUB_REPOSITORY/tree/$VER > distribution/SOURCE_URL.txt
        npm run version
    - uses: actions/upload-artifact@v2
      with:
        path: distribution
+   - uses: *some action here*
+     with:
+       files:
+         - distribution
+       release: ${{ needs.Version.outputs.version }}
+       token: ${{ secrets.GITHUB_TOKEN }}

[notlmn]

@notlmn should this be part of https://github.com/notlmn/release-with-changelog

Or we could output release URL from that action, and use that to upload assets to the release using https://github.com/actions/upload-release-asset.

This is what https://github.com/actions/create-release does.

[fregante]

Moved to https://github.com/fregante/browser-extension-template/issues/59