Turn the buckets of an order into orders

Turn an order's line buckets into orders.

Convert buckets into orders, one order per NON-EMPTY bucket. Each bucket stands alone: a bucket that fails comes back FAILED with its reason while the others still become orders, a bucket that already has an order is reported ALREADY_FINALIZED rather than converted again, so repeating a call cannot create a second order, and a bucket holding no lines comes back SKIPPED_EMPTY and makes no order -- there is nothing to put in it, so that is the right outcome and not a failure. A large request may not fit in one call -- a bucket the call ran out of capacity before reaching comes back with outcome NOT_REACHED, and the buckets already finalized are safe, so call again until no NOT_REACHED comes back. On each later call send bucketRefs listing the buckets still to do: every NOT_REACHED one, and none that came back FAILED. The two are different and the difference matters -- NOT_REACHED was never tried, while FAILED was tried and refused, usually by one of the org's own validation rules, so it fails again every time and with allDraft each call pays to find it before it reaches new work (QA measured 60 buckets with two bad ones: 6 calls repeating allDraft, 3 when the failed ones were left out). Tell the user which buckets failed and why, rather than retrying them. asyncJobIds lists background jobs (start-date recalculation) that must finish before the orders are settled. activateOrders activates the orders this call creates, as it creates them; leave it off unless the user asked for that. It does NOT activate an order that an earlier call already made: that bucket is ALREADY_FINALIZED and its order stays as it was, so activating it afterwards is a separate step on the order itself.