Add runAs to import job Queue Task

[eileenmcnaughton]

Overview

Builds on #24761 to ensure runAs is saved in the import queue job.

Before

The user to run the import as is not stored

After

As shown in the test & this IDE screenshot - the runAs is stored per #24761

In stepping through this test I was able to verify it is honoured - although I have not yet gotten the queue to process in the background via coworker

Technical Details

Comments

[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]

@totten this works on the storage side - per my comments on https://lab.civicrm.org/dev/coworker/-/commit/d92fe0892b2602a99df78ed7f74b381925d481eb I do think a user with permission to run the Queue.runItems api should have the items run in the intended user context & hence the handling for runAs should be there

[totten]

I did some r-run for contact-more-than-100-rows.csv, looking from a few angles:

• Inspect the content of civicrm_queue -- and it does show the records with the runAs filled in.
• Run the import in the foreground (normal/default)
• Run the import in the background (cv vset enableBackgroundQueue=1) with either:
  • Manual API calls: cv api4 --user=admin Queue.runItems queue=user_job_1 (three times)
  • coworker with this MR: https://lab.civicrm.org/dev/coworker/-/merge_requests/2 (that MR has more details about experimental procedure)