Make Che-Code CI build more stable when downloading artifacts from api.github.com

[azatsarynnyy]

Is your task related to a problem? Please describe

Che-Code build has external dependencies downloaded from api.github.com.
Often, downloading process is failed with the error:

#12 34.11 GET https://api.github.com/repos/microsoft/ripgrep-prebuilt/releases/tags/v13.0.0-4
#12 34.11 Deleting invalid download cache
#12 34.11 Downloading ripgrep failed: Error: Request failed: 403

For more details, see https://github.com/che-incubator/che-code/actions/runs/4140287034/jobs/7158796952.

It used to be a minor issue for the GitHub Workflow-based CI until we included Che-Code into the overall Che release flow.
During the Che release, Che-Code build error breaks the release process and requires rerunning it.

Describe the solution you'd like

As it's recommended in microsoft/vscode-ripgrep, we set the GITHUB_TOKEN environment variable:

• Increase GH API rate limit when downloading vscode-ripgrep che-incubator/che-code#170
• Increase GH API rate limit when downloading vscode-ripgrep che-incubator/che-code#174

After setting the GITHUB_TOKEN, we haven't noticed any downloading issues for about a week (Feb 2 - Feb 8).
But, after Feb 8, the problem became relevant again.
We need to investigate if the GITHUB_TOKEN environment variable is propagated correctly to microsoft/vscode-ripgrep.

Describe alternatives you've considered

It may be helpful to check how the problem is solved upstream, for microsoft/vscode CI build.

Additional context

https://github.com/microsoft/vscode-ripgrep/blob/bc5cb922416b4ee0aacf4c0252e42ac78c7ed7e9/lib/postinstall.js#L77

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[azatsarynnyy]

/remove-lifecycle stale

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.