rabbit_khepri: Rename misleading adv_delete() to adv_delete_many()

[Why]
This wrapper was calling `khepri_adv:delete_many()`, not
`khepri_adv:delete()` as the name was suggesting. They are not the same
function and have not the same behaviour.

This led to a performance issue with the branch that replaces the
"delete queue" transaction by a simple delete (#14902) that was related
to this confusion.

[How]
The wrapper is renamed to reflect the Khepri API being called.

While here, add a `rabbit_khepri:adv_delete()` wrapper that calls the
similarily named Khepri API.

(cherry picked from commit 0d3edce)
(cherry picked from commit 77cdf87)

Author: dumbbell

deps/rabbit/src/rabbit_db_rtparams.erl

@@ -357,7 +357,7 @@ delete_vhost_in_mnesia_tx(VHostName) ->
 delete_vhost_in_khepri(VHostName) ->
     Pattern = khepri_vhost_rp_path(
                 VHostName, ?KHEPRI_WILDCARD_STAR, ?KHEPRI_WILDCARD_STAR),
-    case rabbit_khepri:adv_delete(Pattern) of
+    case rabbit_khepri:adv_delete_many(Pattern) of
         {ok, NodePropsMap} ->
             RTParams =
             maps:fold(

deps/rabbit/src/rabbit_khepri.erl

@@ -156,6 +156,7 @@
 
          delete/1, delete/2,
          adv_delete/1, adv_delete/2,
+         adv_delete_many/1, adv_delete_many/2,
          clear_payload/1, clear_payload/2,
 
          transaction/1, transaction/2, transaction/3,
@@ -1262,6 +1263,13 @@ adv_delete(PathPattern) ->
     adv_delete(PathPattern, #{}).
 
 adv_delete(PathPattern, Options) ->
+    Options1 = maps:merge(?DEFAULT_COMMAND_OPTIONS, Options),
+    khepri_adv:delete(?STORE_ID, PathPattern, Options1).
+
+adv_delete_many(PathPattern) ->
+    adv_delete_many(PathPattern, #{}).
+
+adv_delete_many(PathPattern, Options) ->
     Options1 = maps:merge(?DEFAULT_COMMAND_OPTIONS, Options),
     khepri_adv:delete_many(?STORE_ID, PathPattern, Options1).