[CI] Add exclusions for release branches

[pazone]

What does this PR do?

UpdateCLI ESS version pinning: Adds exclusions for release branches because we decided to merge them later.
The exclusions must be removed when the backports are merged
Fixes a typo in pipeline name

Why is it important?

Fixes a regression #8352

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

[v1v]

LGTM.

I ran https://github.com/elastic/elastic-agent/actions/runs/15686671952 but it will fail as the fix is not in main yet, but the exclude branches should work.

However, can you run the updatecli command to validate if your changes are good? That's something we have done in some other PRs:

• #8359
• #8288
• #8211

Thanks

[v1v]

Actually, the GH workflow for this feature branch, worked as expected and created #8543