fix: Update GitLab configuration page

[vinokurig]

Signed-off-by: Igor Vinokur [email protected]

What does this pull request change

Update GitLab oAuth configuration page.

What issues does this pull request fix or reference

fixes eclipse-che/che#21435

Specify the version of the product this pull request applies to

Pull request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

• Any procedure:
  • Successfully tested.
• Any page or link rename:
  • The page contains a redirection for the previous URL.
  • Propagate the URL change in:
    • Dashboard default branding data
    • Chectl constants.ts
• Builds on Eclipse Che hosted by Red Hat.
• the Validate language on files added or modified step reports no vale warnings.

[github-actions]

Click here to review and test in web IDE:

[themr0c]

Is the feature for Che 7.50, or does it work already on Che 7.46?

[themr0c]

In the corresponding issue I see:

We can configure only SAAS or on-premises version with the current oAuth provider.

I believe we should add this information in the docs as well. Something like:

To enable users to work with a remote Git repository that is hosted using one GitLab instance:

[vinokurig]

Is the feature for Che 7.50, or does it work already on Che 7.46?

It already works since the gitlab oAuth is added

[vinokurig]

@themr0c

In the corresponding issue I see:

We can configure only SAAS or on-premises version with the current oAuth provider.

I believe we should add this information in the docs as well. Something like:

To enable users to work with a remote Git repository that is hosted using one GitLab instance:

I think from this PR it is clear what to do if admin wants to use the SAAS OR onpremises version. I don't think it is a good idea to describe that we doesn't support using both instances as it would only confue the reader.