Transition Requisition state to WITHDRAWN when Measurement is cancelled or failed

[SanjayVas]

If a Measurement is put into the CANCELLED or FAILED state by another actor, the CMMS public API provides no way for the DataProvider to determine from the Requisition resource that it can no longer be fulfilled. The DataProvider will get a FAILED_PRECONDITION error when attempting to fulfill, but the Requisition state will remain UNFULFILLED.

This is an API design flaw. The fix probably involves adding a new Requisition state to the public API.

• feat!: Add WITHDRAWN state to Requisition cross-media-measurement-api#212
• build: Add [email protected] bazel-registry#53
• feat!: Update cross-media-measurement-api dep for Requisition.State.WITHDRAWN #1746

[SanjayVas]

It turns out this isn't entirely true, as Requisition has a denormalized measurement_state field. It's still better to have this be encapsulated in Requisition state rather than having to check both fields. This way the caller doesn't have to inspect the error to determine whether it's due to Requisition state or Measurement state.