Refactor Collection Reorder Mutation for Incremental Moves

The collectionReorderProducts mutation’s description and arguments were rewritten to clarify that only moved products should be sent, that moves are applied sequentially, and that newPosition is a zero‑based index evaluated after each prior move; the mutation now returns a job object. The moves list’s documentation was updated to emphasize sending only changed products, allowing non‑unique newPosition values and moving items to the end if the value exceeds the list length. The mutation’s return type remains CollectionReorderProductsPayload. Additional schema changes include converting CheckoutAndAccountsAppConfiguration.brandingConfiguration from a raw JSON scalar to a typed CheckoutBranding object, removing the resourceType field from CustomerPaymentMethod, and adding several new enum values for various error codes (TAG_EXCEEDS_MAX_LENGTH, ACTIVATION_FAILED, etc.). A new field disputeEvidence was added to ShopifyPaymentsDispute to expose dispute evidence details, and a set of LENDING‑related transaction types was added to ShopifyPaymentsTransactionType. The enum StagedUploadTargetGenerateUploadResource now includes DISPUTE_FILE_UPLOAD. Finally, the entire MandateResourceType enum was removed from the schema. Developers must adjust mutation payloads for collection reordering, update type handling for the new branding object, and account for the removed field and added enums in error handling and transaction logic.