[lukaszsamson]

elixir_sense bump

Updates elixir_sense to a15a1f4b, picking up:

• Handle :local_or_var inside struct dot in SurroundContext.to_binding elixir_sense#345: hover crash on %var.foo{} (inside_dot_to_binding({:local_or_var, _}, _) FunctionClauseError)
• Return [] instead of raising on corrupt beam in Normalized.Typespec elixir_sense#346: completion/signature help crash when :beam_lib raises on a corrupt or half-written .beam
• Fix locator for function defined by macro ending with ? or ! elixir_sense#344

Flaky debug adapter tests (seen on Elixir 1.20 / OTP 29)

debugger_test.exs and exunit_formatter_test.exs point the group leader of the global ElixirLS.DebugAdapter.Output process at a PacketCapture started with start_link from the test process. When the test process exits, the capture dies with it, before on_exit restores the group leader. An async request finishing in that window (e.g. a dap_request telemetry event for evaluate / continue) makes Output write to a dead group leader and stop with :terminated:

[error] GenServer ElixirLS.DebugAdapter.Output terminating
** (stop) :terminated
Last message (from #PID<...>): {:send_event, %GenDAP.Events.OutputEvent{... "elixir_ls.dap_command" => "evaluate" ...

Output is not supervised, so every following test fails in setup:

** (ArgumentError) errors were found at the given arguments:
  * 1st argument: not a pid
  :erlang.process_info(nil)
  test/debugger_test.exs:29: ElixirLS.DebugAdapter.ServerTest.__ex_unit_setup_1/1

The fix adds an unlinked PacketCapture.start/1. The tests now use it and stop the capture in on_exit after the group leader is restored.

Order-dependent implementation locator test

find implementations of behaviour module matched the result list positionally, but the order comes from :code.all_loaded/0 and is not deterministic. It failed on master (Elixir 1.20 / OTP 29 / windows). The test now sorts the results before matching.