ci: Migrate the release workflow from CircleCI to GitHub Actions

[SajidAlamQB]

Description

Related to: #176

Following kedro-org/kedro#2153, we also need to migrate the release workflow to GA.

Development notes

Tested on forked repo of kedro-plugins, you can find the example release workflow running here.

To fully work this, I will need the kedro-orgs pypi API key and GitHub access token and add them to the kedro-plugins repo secrets.

[17-05-23]
Here is the latest workflow running on my fork

Checklist

• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the relevant RELEASE.md file
• Added tests to cover my changes

[ankatiyar]

This looks good! We should add a step for running the unit tests, linters and e2e tests before publishing a release. To that end, it might be worth dividing the workflow into separate jobs like -

jobs:
  check-version: 
  (Checks if the version was updated and the new version exists on PyPi, set package_name)
  test: 
    needs: check-version
  (Reuse the `check-plugin.yml` workflow to run tests)
  build: 
    needs: check-version
  (Build only for one version of python?)
  release:
    needs: [test, build]
    steps:
      - name: GitHub release
      - name: PyPi release

check-plugin.yml currently runs all the tests on all versions of python but we can modify that in a separate PR to accept which python versions to run tests on just like it accepts plugin name from the "caller" workflow so we don't have to run all the tests 4 times.

[noklam]

It looks ready to me! One last minor comment is usually we set ENV variable with CAPITAL letter,i.e. GITHUB_ENV.

[ankatiyar]

Looks great! 💯

[merelcht]

Two small comments from my side, but overall this looks good 👍