Support Gitlab OAuth 2.0 identity provider API

New feature

Hi! Thanks for using Nextflow and submitting the proposal
for a new feature or the enhancement of an existing functionality.

Would nextflow support gitlab OAuth 2.0 identity provider API to enable cloning of gitlab repo's using following command:
git clone https://oauth2:ACCESS_TOKEN@somegitlab.com/vendor/package.git

Usage scenario

(What's the main usage case and the deployment scenario addressed by this proposal)
this will enable repositories to be pulled and ran with both private tokens and also OAuth token. Passing the user and token(OAuth token) fails and causes an authentication error even if it's a valid way of cloning any private gitlab repositories.

Am personally using a gitlab application to authenticate users and then retrieve an access token which I can then use to access and perform api functions on behalf of the use.

https://docs.gitlab.com/ee/api/oauth2.html

Suggest implementation

https://github.com/nextflow-io/nextflow/commit/da00175dadd3386332ed54f7c2440642a39b3805

This might be closely related and implemented in the https://github.com/nextflow-io/nextflow/commit/da00175dadd3386332ed54f7c2440642a39b3805#diff-d3e1b1e20532a0d163e0ea16fdafc56705b79046d086472505c259f0b54dd00d file by using a conditional to check if user token is either a private token or auth token and running different git clone commands.

(Highlight the main building blocks of a possible implementation and/or related components)

Read the GitLab OAuth 2.0 API documentation and inspect the referenced Nextflow commit and its linked diff. Trace where repository clone credentials are handled, then verify that a GitLab OAuth access token can clone a private repository using the documented URL format.