fix(ui): Stop using the deprecated url format for gitlab instances

[tete17]

The legacy URLs format has been deprecated since february 2023 and now gitlab is make these urls invalid.

Ref: https://docs.gitlab.com/ee/update/deprecations.html#legacy-urls-replaced-or-removed

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (4ce4885) 49.17% compared to head (0ed4d96) 49.18%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #13687   +/-   ##
=======================================
  Coverage   49.17%   49.18%           
=======================================
  Files         248      248           
  Lines       42874    42874           
=======================================
+ Hits        21083    21086    +3     
+ Misses      19689    19687    -2     
+ Partials     2102     2101    -1     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[crenshaw-dev]

Thanks, @tete17!

[crenshaw-dev]

/cherry-pick release-2.7

[crenshaw-dev]

/cherry-pick release-2.6

[crenshaw-dev]

/cherry-pick release-2.5

[gcp-cherry-pick-bot]

Cherry-pick failed with Merge error 566236747474593d4e0d22a0398ffbcca2ff29aa into temp-cherry-pick-3710e2-release-2.6

[gcp-cherry-pick-bot]

Cherry-pick failed with Merge error 566236747474593d4e0d22a0398ffbcca2ff29aa into temp-cherry-pick-3710e2-release-2.5

[tete17]

Hey @crenshaw-dev thanks for the review.

Do you want me to fix the merge conflicts on the 2.5 & 2.6 branhces?

[crenshaw-dev]

That would be great, thanks! You can just open PRs against those branches directly.

[tete17]

Not entirely sure what is the workflow here.

I will cherry pick the commit on local branch on my repo and propose 2 MR against the different release branches. Let me know if I should do it differently.

2.5: #13797
2.6: #13796