A stored procedure named dbo.uspArchiveOrders performs cross-schema DML that the calling application account (an Entra ID contained user named app_worker) is not permitted to execute directly. You want the procedure to run successfully when called by app_worker without granting that user broad permissions on the underlying tables, and without relying on ownership chaining (the procedure touches objects in a different schema with a different owner). Which approach follows least privilege?