ci(dispatch-gate): allow the capability seam moved into sql_dispatch_task

`7102813b8` moved the native DROP ARRAY path out of `sql_loop.rs` into the
new `sql_dispatch_task.rs`, carrying its `authorize_native_task(..)?` ->
`into_physical_task()` pair with it. `sql_loop.rs` is in ALLOWED_REFERENCES
for exactly that seam; the new file is not, so the gate has flagged the moved
call ever since. The call is unchanged: the capability is consumed first and
the raw task is only reached through it, which is the condition the allowlist
documents.

This does not cover the six `into_scope` references also failing on main;
those are a separate finding, reported on the PR.

Author: laksamanakeris

scripts/ci/check_authorized_dispatch.py

@@ -104,6 +104,7 @@
     ("control/array_sync/inbound_propose.rs", "into_scope"),
     ("control/array_sync/snapshot_assembly.rs", "into_scope"),
     ("control/server/native/dispatch/sql_loop.rs", "into_physical_task"),
+    ("control/server/native/dispatch/sql_dispatch_task.rs", "into_physical_task"),
     ("control/server/sync/raft_dispatch/response.rs", "propose_sync_write"),
     ("control/server/sync/raft_dispatch/write.rs", "propose_sync_write"),
     (