Civi::queue() - Add support for 'template' queues

[totten]

Overview

Suppose you are in the habit of making separate queue-instances for different batches of work. However, you want to allow the sysadmin to configure options like type, batch_limit, and retry_interval.

Solution: Make a template

After

// Use the API to register a template, eg
\Civi\Api4\Queue::create()->setValues([
  'name' => 'my-example',
  'is_template' => TRUE,
  'type' => 'Sql',
  'error' => 'abort',
  'retry_limit' => 5,
  'retry_interval' => 60,
])->execute();

// Later, create a queue from the template
$q = Civi::queue('new-queue', ['template' => 'my-example']);
assert($q inherts the  'type', 'error', 'retry_limit', etc from the template)

Comments

I'm ambivalent about how to mark a template - eg:

• Easier patch: Use status=>template
• Match other entities: Use a new field is_template=>1

[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).

[eileenmcnaughton]

I think is_template is more correct - but there is precedent for the status method - we do that in Contribution - but in fact I think we do BOTH there because we felt that was an especially risky entity. I'm not opposed to the easy route - but suspect we might need to do another alter in which case that might tip it away from easer

[totten]

@eileenmcnaughton Converted patch from status=>template to is_template=>1. Rebased. Updated description.

[eileenmcnaughton]

test this please

[eileenmcnaughton]

test this please

[eileenmcnaughton]

fail is unrelated - fix is in #23751