(dev/core#1304) Queues - Define 'status' and 'error' columns

[totten]

Overview

This is a follow-up to 5.47's introduction of civicrm_queue (persistent queue registrations). It allows extra options to specify the status and error mode.

Contributes to https://lab.civicrm.org/dev/core/-/issues/1304. Extracted from #22762. ping @eileenmcnaughton

Technical Details

• It adds two new MySQL columns for civicrm_queue:
  • status: Differentiate between active queues (where tasks should run automatically) and various inactive queues (draft, complete, aborted)
  • error: Determine whether errors are fatal (error=>abort) or non-fatal (error=>delete). The fatal approach is more appropriate if you have a short-term queue with a limited scope of inter-dependent tasks. The non-fatal mode is more appropriate if you have a long-term queue that services many independent tasks.
• The new fields will be important for persistent/registered queues that run tasks automatically in the background. Therefore, Civi::queue() will accept and validate status and error. (However, these fields do not matter if you have older style code.)
• The upgrader will backfill values of status and error. (There are some code-comments discussing details further.)

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).