Back-Porting Jenkins Semaphore migration changes

[VanamalaNarasimhaBhargav]

1. During Jenkins to Semaphore migration service-bot added some changes to an exiting PR chore: update repo by service bot #67.
2. Earlier this PR was merged as is but we later realised all changes from this PR were not required so this PR is reverted at Revert "chore: update repo by service bot" #75 & only required changes are cherry-picked in this PR.
3. How to verify? Ensure all changes from .semaphore folder in the PR chore: update repo by service bot #67 are picked up

Will make sure that the changes are reviewed by c3 & cp-build team.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqube-confluent]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (0.00% Estimated after merge)
• No duplication information (0.00% Estimated after merge)

Project ID: control-center-images

View in SonarQube