Guard against missing tenant context in jobs

Fail fast when a job runs without the tenant payload injected by
`perform_later`, instead of crashing later on `context["tenant"]`.

This makes accidental `perform_now` usage easier to diagnose:

> Missing tenant context, use perform_later (via
> TenantSwitchEachJob) instead of perform_now

Also avoid enqueueing a job from the Postmark inactive-recipient rescue
path so suppression sync still works in synchronous flows.

Author: thibaudgg

app/jobs/concerns/tenant_context.rb

@@ -19,11 +19,13 @@ def serialize
 
   def with_context(&block)
     context = arguments.pop
+    raise "Missing tenant context, use perform_later (via TenantSwitchEachJob) instead of perform_now" unless context.is_a?(Hash) && context.key?("tenant")
+
     Tenant.switch(context["tenant"]) do
       Current.set(context["current"], &block)
     end
   ensure
-    set_context(context)
+    set_context(context) if context
   end
 
   private

app/models/mail_delivery/email.rb

@@ -39,7 +39,7 @@ def process!
         mail_delivery.store_preview_from!(message)
       end
     rescue Postmark::InactiveRecipientError
-      Scheduled::PostmarkSyncSuppressionsJob.perform_now
+      EmailSuppression.sync_postmark!(fromdate: 1.week.ago)
       suppressed!
       mail_delivery.store_preview_from!(message)
     rescue Postmark::InvalidEmailRequestError