Reporting Progress on Fulfillment Orders & Payment Processing Policies

The schema now exposes the fulfillmentOrderReportProgress mutation, allowing fulfillment services to mark an order as in‑progress or report progress, along with optional notes via the new FulfillmentOrderReportProgressInput. The mutation returns the updated FulfillmentOrder and a list of FulfillmentOrderReportProgressUserError objects, covering status and ownership validation errors. Two new FulfillmentOrderAction enum values—REPORT_PROGRESS and MARK_AS_IN_PROGRESS—enable finer‑grained action control. Webhook topics FULFILLMENT_ORDERS_PROGRESS_REPORTED and FULFILLMENT_ORDERS_MANUALLY_REPORTED_PROGRESS_STOPPED are added for real‑time progress notifications. A new enum SubscriptionBillingAttemptPaymentProcessingPolicy introduces two payment options, and the arguments paymentProcessingPolicy are added to both subscriptionBillingCycleBulkCharge and subscriptionBillingCycleCharge mutations for explicit payment‑handling behavior. Developers should update request payloads to include the new args where needed and handle the expanded error codes in their fulfillment logic.