Use gitlab-shell v3.6.2

What does this MR do?

Bump gitlab-shell to v3.6.2 to be able to enable GIT_TRACE_PERFORMANCE output to a log file

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• CHANGELOG entry added
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if you do - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Relates #22053 (moved)

This depends on gitlab-shell!91 (merged). @pacoguzman Please consider making it a WIP until gitlab-shell!91 (merged) is merged and v3.5.1 is actually tagged. :)

Marked this merge request as a Work In Progress

@rymai done!

Added 563 commits:

• e6ac48e7...1aca3670 - 562 commits from branch master
• e7ab6b70 - Use gitlab-shell v3.6.2 (GIT TRACE logging)

Changed title: WIP: Use gitlab-shell v3.5.1 → WIP: Use gitlab-shell v3.6.2

@pacoguzman The tag now exists!

Unmarked this merge request as a Work In Progress

Added ~18308 label

Reassigned to @rymai

Not work in progress anymore, thanks @rymai for let me know

Thanks @pacoguzman!

Milestone changed to %8.13

Status changed to merged

Mentioned in commit bac56e3b