[Automation] Bump product version numbers

[elastic-observability-automation]

Bump release versions in the config/versions.yml

Update config/versions.yml edot-node 1.4.0

change detected: * key "$.versioning_systems.edot_node.current" updated from "1.3.0" to "1.4.0", in file "config/versions.yml"

v1.4.0

## Changelog

### Features and enhancements

* The Elastic-authored `@elastic/opentelemetry-instrumentation-openai`
  instrumentation has been [upstreamed to OpenTelemetry](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-openai/).
  EDOT Node.js now uses the `@opentelemetry/instrumentation-openai` package
  to instrument `openai`. The newer package supports instrumenting openai@5 --
  the current major version.
  [#1015](https://github.com/elastic/elastic-otel-node/pull/1015)

    * If you were using `@elastic/opentelemetry-instrumentation-openai` with the
      `OTEL_NODE_ENABLED_INSTRUMENTATIONS` or `OTEL_NODE_ENABLED_INSTRUMENTATIONS`
      environment variables, you should switch to using `openai`. The old value
      will still work until the next major release.

### Fixes

* Update to latest `@opentelemetry/*` dependencies ([#1027](https://github.com/elastic/elastic-otel-node/pull/1027)), which includes a [fix](https://github.com/open-telemetry/opentelemetry-js/pull/5917) for a bug in `@opentelemetry/otlp-exporter-base@0.204.0` that could break bundling.

---

[README](https://github.com/elastic/elastic-otel-node/tree/main/packages/opentelemetry-node#readme) | [Full Release Notes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/index.md) | [Breaking Changes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/breaking-changes.md)

Update config/versions.yml stack 9.1.4

1 file(s) updated with "$1 9.1.4": * config/versions.yml

Update config/versions.yml edot-collector 9.1.4

change detected: * key "$.versioning_systems.edot_collector.current" updated from "9.0.7" to "9.1.4", in file "config/versions.yml"

v9.0.7

Downloads: https://elastic.co/downloads/elastic-agent
Release notes: https://www.elastic.co/docs/release-notes/fleet#fleet-elastic-agent-9.0.7-release-notes

v9.1.4

Downloads: https://elastic.co/downloads/elastic-agent
Release notes: https://www.elastic.co/docs/release-notes/fleet#fleet-elastic-agent-9.1.4-release-notes

Update config/versions.yml apm_agent_java 1.55.1

change detected: * key "$.versioning_systems.apm_agent_java.current" updated from "1.55.0" to "1.55.1", in file "config/versions.yml"

v1.55.1

[Release Notes for 1.55.1](https://www.elastic.co/docs/release-notes/apm/agents/java#elastic-apm-java-agent-1-55-1-release-notes)
  ### ARNs of the APM Java Agent AWS Lambda Layer

|Region|ARN|
|------|---|
|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-java-ver-1-55-1:1|
|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-java-ver-1-55-1:1|

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!

[colleenmcginnis]

We should not update this to the most recently published version if it's a patch for a previous minor. I'm curious if there's there a way to handle this in the automation or should we rely on PR reviewers to catch this kind of error? (I don't know anything about how the automation works. 🙂)

[theletterf]

Good catch. I'll see if I can improve this.

[theletterf]

PR: #1929