chore(deps): update dependency nebulex to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
nebulex (source)	dev	major	~> 2.1 → ~> 3.0

---

Release Notes

elixir-nebulex/nebulex (nebulex)

v3.0.4

Compare Source

Full Changelog

Documentation

• Added usage-rules/architecture.md covering Nebulex's layer
  boundaries, key design decisions, and non-negotiable contribution
  rules. Used to bootstrap agent-assisted development sessions.
• Tightened and reconciled the agent rule files: unified Rule Index
  and Rule Precedence in workflow.md, aligned CHANGELOG policy with
  CONTRIBUTING.md, clarified validation commands, and fixed a
  number of consistency issues surfaced by cold-session simulations.

v3.0.3

Compare Source

Full Changelog

Documentation

• Added usage-rules/architecture.md covering Nebulex's layer
  boundaries, key design decisions, and non-negotiable contribution
  rules. Used to bootstrap agent-assisted development sessions.
• Tightened and reconciled the agent rule files: unified Rule Index
  and Rule Precedence in workflow.md, aligned CHANGELOG policy with
  CONTRIBUTING.md, clarified validation commands, and fixed a
  number of consistency issues surfaced by cold-session simulations.

v3.0.2

Compare Source

Full Changelog

Adapter changes

• [nebulex_distributed] Added new Nebulex.Adapters.Replicated push-based
  replicated cache adapter with eager replication, "newer version wins"
  conflict resolution, bootstrap on node join, and optional anti-entropy
  reconciliation. See nebulex_distributed v3.2.0 for details.

Documentation

• Updated the official adapters guide to include the Replicated adapter.

v3.0.1

Compare Source

Full Changelog

Enhancements

• Added usage-rules/ folder to the Hex package for agent-assisted
  development workflows.
• Fixed CI workflow: split Hex/Rebar install from dependency fetching,
  improved PLT cache key to include Elixir/OTP versions and mix.lock
  hash, fixed dialyzer step to run regardless of PLT cache status,
  and bumped GitHub Actions to v4.

v3.0.0

Compare Source

Full Changelog

Enhancements

• [Nebulex.Event.CacheEntryEvent] Forward per-command
  :telemetry_metadata as :extra_metadata within the event's
  :metadata map. This allows event listeners to inspect metadata
  markers without disabling telemetry entirely. The metadata type
  is now always a map (previously keyword() | map()).
  #​253.
• [Nebulex] Add "Installation" section to the main module docs
  clarifying that adapter dependencies (e.g., :nebulex_local) must
  be added explicitly in mix.exs.
• [Nebulex] Improve main module docs structure: rename "Caches" to
  "Usage" and add "What's next" section linking all guides in a
  logical learning progression.
• [Nebulex.Cache.Options] Remove misleading default: false from
  the runtime :telemetry option schema. The actual default comes
  from the cache's global :telemetry setting in adapter_meta,
  not the option schema.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Zhukikov]

I believe that there's at least one incompatible change in nebulex v3 that is causing opentelemetry_nebulex to break.

16:12:58.048 [error] Handler {OpentelemetryNebulex, [:cache], :command_start} has failed and has been detached. Class=:error
Reason={:badkey, :function_name,

elixir-nebulex/nebulex@5359c0f
- Rename the Telemetry metadata field from `:function_name` to `:command`.

[tsloughter]

@Zhukikov thanks. Lookslike it runs no nebulex tests in CI :(

[yordis]

I wouldn't merge this one, I do not believe most people already upgraded to v3, we are using it personally and the movement isn't that trivial, given the risk of it.

[yordis]

I would hold on this one until CI is sorted out