[updatecli] Bump elastic stack version to 9.3.0-0bfc0c7d

[elastic-observability-automation]

What

Bump elastic stack version to 9.3.0-0bfc0c7d

---

Bump elastic-stack to latest snapshot version

Update k8s stack yaml files

3 file(s) updated with "version: 9.3.0-0bfc0c7d-SNAPSHOT": * testing/infra/k8s/base/stack/apm-server.yaml * testing/infra/k8s/base/stack/elasticsearch.yaml * testing/infra/k8s/base/stack/kibana.yaml

Update docker-compose.yml

1 file(s) updated with "$1:9.3.0-0bfc0c7d-SNAPSHOT": * docker-compose.yml

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label. Could you fix it @elastic-observability-automation[bot]? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[kruskall]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[kruskall]

@Mergifyio queue

[mergify]

queue

🛑 Configuration not compatible with a branch protection setting

The branch protection setting Require branches to be up to date before merging is not compatible with draft PR checks. To keep this branch protection enabled, update your Mergify configuration to enable in-place checks: set merge_queue.max_parallel_checks: 1, set every queue rule batch_size: 1, and avoid two-step CI (make merge_conditions identical to queue_conditions). Otherwise, disable this branch protection.