Resolves #5157
Impact: major
Type: refactor

All of the UI work, queries, mutations and tests have already been reviewed and merged in the PR's listed below. Therefore an in-depth test of all NEW functionality / code here is not the goal of this PR. The goal of this particular PR is to make this new Orders UI the official Orders UI (seen in this Routing change), and to remove the old UI, meteor methods, and related files.

Changes already implemented:

• refactor: update styling of orderCard header section, move details to sidebar #5240
• feat: add resolver to get displayStatus from database #5236
• chore: update styles for MUI Typography to match designs #5235
• feat: add landing page for catalyst #5226
• chore: add language to shop query #5203
• feat: add read-only version of orders 2.0 to break up PR's #5202
• add approveOrderPayments graphql mutation #5201
• feat: DangerButton and ConfirmButton components #5200
• feat: new button component to wrap MUI button with isWaiting loading state #5266
• refactor: payments section of Orders 2.0 #5279
• refactor: fulfillment section of Orders 2.0 #5302
• feat: add refunds GraphQL query #5352
• feat: add createRefund GraphQL mutation  #5354
• refactor: refunds section of Orders 2.0 #5405

Issue

Operator UI Orders panel currently

• uses our old Meteor methods to preform necessary functions, which don't include new mutations to split fulfillment groups and move items between them
• isn't updated to easily use multiple fulfillment methods, it currently combines all products into a single group

Solution

Update the Orders admin to use GraphQL for all data, instead of the existing Meteor methods. In addition, update the panel to preform actions against multiple fulfillment groups, instead of a single combined Order for all groups.

Breaking changes

Meteor methods will no longer work. All orders functionality is now GQL.

Testing

• Add orderStatusLabels to the Shops collection shop object. This will provide translations for all the Chip style order status badges in the Orders Fulfillment UI.

"orderStatusLabels": {
    "new" : [ 
        {
            "language" : "en",
            "label" : "Order received"
        }, 
        {
            "language" : "es",
            "label" : "Recibido"
        }
    ],
    "coreOrderWorkflow/processing" : [ 
        {
            "language" : "en",
            "label" : "Order received"
        }, 
        {
            "language" : "es",
            "label" : "Recibido"
        }
    ],
    "coreOrderWorkflow/completed" : [ 
        {
            "language" : "en",
            "label" : "Shipped"
        }, 
        {
            "language" : "es",
            "label" : "Enviado"
        }
    ],
    "coreOrderWorkflow/canceled" : [ 
        {
            "language" : "en",
            "label" : "Canceled"
        }, 
        {
            "language" : "es",
            "label" : "Cancelado"
        }
    ],
    "coreOrderWorkflow/picked" : [ 
        {
            "language" : "en",
            "label" : "Picked"
        }
    ],
    "coreOrderWorkflow/packed" : [ 
        {
            "language" : "en",
            "label" : "packed"
        }
    ],
    "coreOrderWorkflow/shipped" : [ 
        {
            "language" : "en",
            "label" : "shipped"
        }
    ]
}

• Create orders
• See that the ProductImage works as it should, as this component was moved out of the Orders package and into Checkout where it's used: 3356ff1
• See the orders appear correctly in the Orders table
• See that when you click an order, it goes to the new UI, not the old UI, and the url is just /orders/{order-id}, not /orders-beta/{order-id}
• Run through any fulfillment scenarios you wish, but as mentioned, these have already been fully tested and merged into the codebase in the above listed PR's.