fix(ci): semantic-release

[ethan-ozelius-contentful]

Summary

1. Fix semantic-release, which is running into the following github token permissions error:

[6:15:04 PM] [semantic-release] › ✘  Failed step "fail" of plugin "@semantic-release/github"
[6:15:04 PM] [semantic-release] › ✘  ENOGHTOKEN No GitHub token specified.
A GitHub personal token (https://github.com/semantic-release/github/blob/master/README.md#github-authentication) must be created and set in the GH_TOKEN or GITHUB_TOKEN environment variable on your CI environment.

Please make sure to create a GitHub personal token (https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) and to set it in the GH_TOKEN or GITHUB_TOKEN environment variable on your CI environment. The token must allow to push to the repository contentful/contentful.js.

[6:15:04 PM] [semantic-release] › ✘  ENOGHTOKEN No GitHub token specified.
A GitHub personal token (https://github.com/semantic-release/github/blob/master/README.md#github-authentication) must be created and set in the GH_TOKEN or GITHUB_TOKEN environment variable on your CI environment.

Please make sure to create a GitHub personal token (https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) and to set it in the GH_TOKEN or GITHUB_TOKEN environment variable on your CI environment. The token must allow to push to the repository contentful/contentful.js.

Resolution is to retrieve the github token, using vault secret and then pass that as an env var to the npm run semantic-release step.

2. Add github tags/releases that will be authored by Contentful automation bot.

3. remove unccessary steps from release.yaml

• Restore the build folders
• name: Setup Chrome

[contentful-automation]

🎉 This PR is included in version 11.8.13 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀