BE-7028 Update V2 order skip logic to match V1

Tasks

workprojectep411be7028unskiphungryrootapiv2

workprojectep411be7028unskiphungryrootapiv2

After moving the skip order logic in the CX tool to the V2 endpoint in

discovered between the V1 and V2 logic. Ellen Reed those differences are:

v2 does not validate whether order is past cutoff and therefore unskippable

calculate preferred date gets a schedule but schedule could be past cutoff;

preferred_date validation just checks if it's valid for the zipcode

I think our UI in both the CX tool and web/mobile hide the "unskip" button if

it's past cutoff, but people can likely still unskip if they're on a stale page.

The API should validate that the order is not past cutoff.

V1 logs a DatadogMetric for ORDER_UNSKIP. I don't know if we still use those, so

this might be fine

V2 hard codes is_cx_action = False. Unless you know they no longer use this

attribute, my understanding is that they use this in Braze to email the customer

about the status change but only if it originated from CX

Acceptance Criteria

When an order status is changed to unskipped by a PATCH to the V2 order detail

endpoint an error should be returned if the order is past cutoff

(order.is_editable == False)

The V2 endpoint should accept a GET parameter is_cx_action boolean rather than

using a default False value. This is already passed to braze events in the view.