github-actions: updatecli bump for specific branches

[v1v]

What does this PR do?

Add a branch name in the Slack error message.
Checkout the branch with the upatecli pipeline changes to fix this error

Why is it important?

This will help when configuration changes are different between branches.

However, this will require maintaining the updatecli pipeline in different branches too.

#8359 introduced the support for .buildkite/bk.integration-fips.pipeline.yml but #8035 was only backported to 8.19. Hence it failed for 9.0, 8.18 and 8.17.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[pkoutsovasilis]

/test

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 420921d

cc @v1v