Create tests to check 'Git zero-config' flow as PR checks

[artaleks9]

What does this PR do?

• implements launch tests to check 'Git zero-config' flow as PR check in Openshift Ci infrastructure -> Add new component 'che-server' openshift/release#37823
• Creates Dockerfile to configure ci-operator -> Create 'Dockerfile' to configure ci-operator #495
• Creates base set of tests to check repositories of GitLab.com, Bitbucket.org, GitHub.providers which includes:

1. there are created test accounts with a public and private repositories with a simple devfile.yaml inside, like:

schemaVersion: 2.1.0
metadata:
  name: public-repo-wksp-testname

or

schemaVersion: 2.1.0
metadata:
  name: private-repo-wksp-testname

2. a check of factory resolver by API for public/private repository git providers with NO setup PAT/OAuth
3. launch a workspace with test git provider Url repository and check of clone a project as git flow with NO setup PAT/OAuth

• Adds additional file htpasswd Provider.yaml needed to configure environment
• Adds additional file devworkspace-test.yaml needed to create a test workspace:

kind: DevWorkspace
apiVersion: workspace.devfile.io/v1alpha2
metadata:
  name: ws-name
spec:
  started: true
  template:
    projects:
      - name: project-name
        git:
          remotes:
            origin: git-repo-url
  contributions:
    - name: che-code
      uri: https://eclipse-che.github.io/che-plugin-registry/main/v3/plugins/che-incubator/che-code/latest/devfile.yaml
      components:
        - name: che-code-runtime-description
          container:
            env:
              - name: CODE_HOST
                value: 0.0.0.0

• Upadtes 'build-pr-check.yml' GitHub action to get che-server docker image with PR changes:

Screenshot/screencast of this PR

What issues does this PR fix or reference?

eclipse-che/che#21753

How to test this PR?

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.

[artaleks9]

/retest

[dmytro-ndp]

@artaleks9 : do you have logs of successful and failed PR check execution to share?
It's needed to review test scenario execution, and make sure there is no false positive / negative test verdict at the end.

It's also not clear which particular scenario the test is executing:

• which test repo is used to run the test
• which factory URL is used to run the test
• will there PAT or OAuth flow (accepted, refused) scenario be covered?

[artaleks9]

• Do you have logs of successful and failed PR check execution to share?
  Successful Logs:
  -- bitbucket.org flow
  -- github.com flow
  -- gitlab.com flow
  Failed Logs:
  -- gitlab.com flow
  -- bitbucket.org flow

• Which test repo is used to run the test?
  Bitbucket.org:
  -- https://chepullreq1@bitbucket.org/chepullreq/public-repo.git
  -- https://chepullreq1@bitbucket.org/chepullreq/private-repo.git
  GitHub.com:
  -- https://github.com/chepullreq1/public-repo.git
  -- https://github.com/chepullreq1/private-repo.git
  GitLab.com:
  -- https://gitlab.com/chepullreq1/public-repo.git
  -- https://gitlab.com/chepullreq1/private-repo.git

• Which factory URL is used to run the test?
  -- Here there is not factory Url like when use from UI, is used test 'devworkspace-test.yaml' (see the description of the PR ) which has 'git remotes', where is writing the Url of test git repository.
  This is enough to run test workspace and to check a clone/ not clone of a test project.

• Will there PAT or OAuth flow (accepted, refused) scenario be covered?
  This is the end point of the task, it would be cool, if it could be done without UI.
  Honestly, I don't know could we do it without UI, but need to try.
  So I can't say exactly, how it will be. We decided for the start make some simple test, on this moment it is exist:
  -- check of factory resolver by API for public/private repository git providers with NO setup PAT/OAuth
  -- launch a workspace with test git provider Url public/private repository and check of clone a project with NO setup PAT/OAuth.

Updated: I can carefully say, it seems, there is possible to execute setup PAT and check appropriate clone a public/private repository already with PAT.

[svor]

LGTM

[dmytro-ndp]

@artaleks9: thanks for the answers!
I would suggest to express it somewhere, that this MR is introducing some kind of smoke test of factory resolver, to avoid confusing.
E.g., it could be expressed in test name, like test-github-without-oauth-pat-setup-flow.sh

[ibuziuk]

@artaleks9 @dmytro-ndp folks, can we merge this PR now?

[dmytro-ndp]

Looks good to merge.

[artaleks9]

The last updates includes:

• rename exist tests to no-pat-oauth-flow as proposed by @dmytro-ndp
• refactor the method testProjectIsCloned as proposed by @dmytro-ndp
• add the test template pat-secret.yaml to .ci/openshift-ci in che-server repository
• add new tests to check git-flow with PAT setup in .ci/openshift-ci of che-server repository
• update configuration in Openshift CI to add new tests -> Update 'che-server' component
• add new methods to implement PAT setup in the common.sh script :
  -- initialize an <user-che> namespace by che-server API
  -- create the PAT secret in an <user-che> namespace
  -- check the git-credentials in a running workspace

[artaleks9]

/retest

[dmytro-ndp]

New changes look good to merge.

Thanks for the handling feedback, @artaleks9

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: artaleks9, dmytro-ndp, ibuziuk, svor

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment