mergify: support auto-merge for bk.integration-fips.pipeline.yml

[v1v]

What does this PR do?

Add the new BK pipeline to the valid pipelines.

Why is it important?

Missed the new BK pipeline to validate (created at #8035)

Support for other BK pipelines, see https://github.com/elastic/elastic-agent/pull/8465/checks?check_run_id=43966486237

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: 61feb7a

cc @v1v

[v1v]

For the record I tested the auto-approval and auto-merge process at:

• [Automation] Bump EDOT versions v1v/test-mergify#3

I used a subset of the configuration, but so far It worked as expected :)