Guard push-ledger sweeper when appwritePushLedger is absent - #13772

deleteExpiredPushLedger could attempt deletion against projects where appwritePushLedger does not exist, relying on onError handling after entering delete flow. This change aligns the worker with the recommended guard-first pattern by short-circuiting before delete.

• What changed

  • Added an explicit collection-existence check in Deletes::deleteExpiredPushLedger.
  • Return early when appwritePushLedger is missing, preserving existing behavior for projects where it exists.

• Why this matters

  • Avoids delete attempts on non-existent collections.
  • Makes cleanup behavior deterministic and consistent with existing guard-before-delete patterns.

• Code change (core)

  $dbForProject = $getProjectDB($project);
  if ($dbForProject->getCollection('appwritePushLedger')->isEmpty()) {
      return;
  }
  
  $expired = DateTime::addSeconds(new \DateTime(), -1 * 60 * 60 * 24 * 7);
  
  $dbForProject->deleteDocuments('appwritePushLedger', [
      Query::lessThan('$createdAt', $expired),
  ], onError: function (Throwable $th) {
      // Swallow errors (e.g. projects without the push ledger collection).
  });