Authorize GitHub requests with header instead of query parameter

[vinokurig]

What does this PR do?

Use GitHub Authorisation header in GitHub HTTP requests instead of token in query parameter.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

eclipse-che/che#16425

How to test this PR?

1. Setup GitHub Identity provider
2. Start a workspace with GitHub Pull Requests plugin and a project cloned from GitHub by https url.
   You can use this devfile to start a workspace:

apiVersion: 1.0.0
metadata:
  name: wksp-custom-dwdiu
projects:
  - name: che-theia
    source:
      location: 'https://github.com/eclipse/che-theia.git'
      type: git
      branch: master
components:
  - type: chePlugin
    reference: 'https://raw.githubusercontent.com/eclipse/che-plugin-registry/master/v3/plugins/ms-vscode/vscode-github-pullrequest/0.20.0/meta.yaml'
  - type: cheEditor
    reference: 'https://raw.githubusercontent.com/chepullreq4/pr-check-files/master/che-theia/pr-924/simple/che-theia-editor.yaml'

3. Sign-in to the GitHub Pull Requests plugin.

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Happy Path Channel

HAPPY_PATH_CHANNEL=stable

[benoitf]

Hello, the node build is failing

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job console

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:924
che-theia-endpoint-runtime-binary	docker.io/maxura/che-theia-endpoint-runtime-binary:924

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job console

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:924
che-theia-endpoint-runtime-binary	docker.io/maxura/che-theia-endpoint-runtime-binary:924

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job console

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:924
che-theia-endpoint-runtime-binary	docker.io/maxura/che-theia-endpoint-runtime-binary:924

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[benoitf]

Working and token is used in headers

[benoitf]

[crw-ci-test]

[che-bot]

✅ E2E Happy path tests succeed 🎉

See Details

• Jenkins job console

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:924
che-theia-endpoint-runtime-binary	docker.io/maxura/che-theia-endpoint-runtime-binary:924

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.