Drop redundant @deleteRecord on campaigns list mutation

@deleteEdge already removes the deleted campaign from the
connection on the list view, so the extra @deleteRecord was
redundant. The detail page mutation still uses @deleteRecord
since it has no connection to delete from.

Signed-off-by: Bryan Frimin <bryan@getprobo.com>

apps/console/src/pages/organizations/access-reviews/campaigns/AccessReviewCampaignsTab.tsx

@@ -91,9 +91,7 @@ const deleteCampaignMutation = graphql`
     $connections: [ID!]!
   ) {
     deleteAccessReviewCampaign(input: $input) {
-      deletedAccessReviewCampaignId
+      deletedAccessReviewCampaignId @deleteEdge(connections: $connections)
-        @deleteEdge(connections: $connections)
-        @deleteRecord
     }
   }
 `;