[Automation] Bump product version numbers

[elastic-observability-automation]

Bump release versions in the config/versions.yml

Update config/versions.yml edot-node 1.3.0

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

v1.3.0

## Changelog

### Features and enhancements

* Added `@opentelemetry/instrumentation-oracledb` to the default set of instrumentations.

* New Central Configuration settings. Typically these settings are only useful
  for temporary debugging of telemetry.

    * `send_traces`: A boolean to disable/enable sending of trace telemetry (i.e. spans).
    * `send_metrics`: The same, for the metrics signal.
    * `send_logs`: The same, for the logs signal.

  While these are supported in EDOT Node.js, they will only be present in
  "Agent Configuration" UI of Kibana version 9.2 and later.
  [#928](https://github.com/elastic/elastic-otel-node/pull/928)

* New `ELASTIC_OTEL_CONTEXT_PROPAGATION_ONLY` configuration environment variable.
  Set this to `true` to disable sending of spans, but otherwise continue to
  do context propagation. This can be useful in limited conditions to support
  propagating trace-context through a service to downstream services for
  distributed tracing, but not collect spans from the service. (Note that this
  typically results in incomplete or broken traces in Kibana trace viewer.)
  [#928](https://github.com/elastic/elastic-otel-node/pull/928)

### Fixes

### Chores

* OTLP export requests (HTTP flavors only) will include an identifier for EDOT Node.js in the User-Agent header.
  [#982](https://github.com/elastic/elastic-otel-node/pull/982)

---

[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)

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!