fix: Sticking to DNS label standard in branch_slug (Gitlab PR Generators)

[Aym3nTN]

#10622

Building on top of this PR #10698 (not sure if it's the right to do it though)

I had to fix these 2 issues in the gosimple/slug package: gosimple/slug#77 and gosimple/slug#75

link next to the DCO action for instructions on how to resolve this.

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).
• 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).

[codecov]

Codecov Report

Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 45.67%. Comparing base (53a210e) to head (8ba5c3a).
Report is 2482 commits behind head on master.

Files	Patch %	Lines
applicationset/generators/pull_request.go	71.42%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10801   +/-   ##
=======================================
  Coverage   45.67%   45.67%           
=======================================
  Files         236      236           
  Lines       28697    28702    +5     
=======================================
+ Hits        13106    13109    +3     
- Misses      13799    13800    +1     
- Partials     1792     1793    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Aym3nTN]

@crenshaw-dev is it possible to pick this on v2.5 release with this ticket? #9540 (comment)

[crenshaw-dev]

Thanks @Aym3nTN! I proposed an alternative solution here: #10622 (comment)