Map action secrets to dependabot secrets in the eclipse-che/che-server repository

Summary

In order for Dependabot to have access to repository secrets, duplicate next secrets:

• secrets.QUAY_USERNAME
• secrets.QUAY_PASSWORD
• secrets.DEVELOCITY_API_TOKEN

from the Actions section to Dependabot secrets in the https://github.com/eclipse-che/che-server repository settings:

Steps to reproduce

(How one can reproduce the issue - this is very important)

What is the current bug behavior?

GitHub has restricted the access to action secrets in workflows triggered by dependabot, see https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/

What is the expected correct behavior?

Workflows triggered by Dependabot must be able to read the repository secrets.

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")