Use GITHUB_TOKEN authentication on workflows

[Sherlouk]

Pull Request

Related issue

CI is current very intermittent with predominantly rate limiting errors being thrown.

What does this PR do?

• When GitHub creates a new workflow, it defines a new GITHUB_TOKEN secret which is unique to that individual run. This is managed entirely by GitHub and requires no additional setup by us.
• This GitHub managed token therefore will have fresh rate limits and thus cannot be impacted by other users of the PATs we use right now.
• Ultimately this should lead to a much more reliable test setup where it should never fail to authenticate.

⚠️ This currently uses a local copy of the install script. A subsequent PR has been raised to update the shared script (meilisearch/meilisearch#5216) which will then be used here.
ℹ️ Once the install script is updated, we should look to make this same change on all workflows across the Meilisearch estate, eliminating use of the PAT for testing.

PR checklist

Please check if your PR fulfills the following requirements:

• Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
• Have you read the contributing guidelines?
• Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

[curquiza]

@Sherlouk meilisearch/meilisearch#5216 has been merged, what can we do with this PR now?

[Sherlouk]

So https://install.meilisearch.com/ links to https://raw.githubusercontent.com/meilisearch/meilisearch/latest/download-latest.sh which I believe is driven by the latest tag on the repository. So until we re-tag the main repository, the install script won't be updated.

I could temporarily point to https://raw.githubusercontent.com/meilisearch/meilisearch/main/download-latest.sh (notice main vs latest in the URL), but yeah need to wait for a tag.

[Sherlouk]

Pushed with the updated script (https://raw.githubusercontent.com/meilisearch/meilisearch/main/download-latest.sh) just to demonstrate. Obviously once we re-tag we can revert the curl line back to curl -L https://install.meilisearch.com | sh.

The only necessary change (once tagged), and what will want to be reproduced on every repository (well those which don't use Docker), is:

-      GITHUB_PAT: ${{ secrets.MEILI_BOT_GH_PAT }}
+      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

edit:// looks like a tag was published a few hours ago, but didn't include these changes (see here). Need the updated script to be tagged.

[curquiza]

bors merge

[meili-bors]

Build succeeded:

• linter-check
• integration-tests on macos-latest
• integration-tests on ubuntu-20.04