Sentry.LoggerBackend doesn't take context set by `Sentry.Context.set_extra_context` into account

Environment

How do you use Sentry? self-hosted, but it doesn't matter, error is on the client's side

Which SDK and version? sentry-elixir 8.0.6

Steps to Reproduce

1. Use logger backend with Sentry.Context.set_extra_context
2. Crash
3. No additional info form Sentry.Context.set_extra_context in the sentry issue

Expected Result

:extra is not lost

Actual Result

:extra is lost

it happens because sentry logger backend sets :extra key twice,

1. sentry-elixir/lib/sentry/logger_backend.ex

   Line 104 in a77b709

   extra: %{logger_metadata: logger_metadata(meta, state), logger_level: level},

2. sentry-elixir/lib/sentry/logger_backend.ex

   Line 106 in a77b709

   ] ++ Map.to_list(sentry)

Which results in opts for capture_message like this:

stacktrace: [
   # ...
  ],
  event_source: :logger,
  level: "error",
  # set by logger
  extra: %{logger_level: :error, logger_metadata: %{}},
  result: :none,
  extra: %{
    # set by Sentry.Context.set_extra_context
  },
  tags: %{
    # set by Sentry.Context.set_extra_context
  },
  user: %{
    # set by Sentry.Context.set_extra_context
  }

Note :extra appears twice, and when creating an event, only the first :extra is taken:

sentry-elixir/lib/sentry/event.ex

Line 114 in a77b709

|> Map.merge(Keyword.get(opts, :extra, %{}))

The fix is to merge sentry[:extra] with %{logger_metadata: logger_metadata(meta, state), logger_level: level}.

OK to PR?

[mitchellhenke]

@syfgkjasdkn yes, a PR would be great!

[ccapndave]

I also ran into this problem! I guess @syfgkjasdkn is busy so I will make a PR 👍

[lubien]

Just ran into this issue, would be lovely to see this fix

[nickdichev-firework]

This fix isn't on 8.0.6, right? Are there plans to cut a hex release sometime soon?