VACMS-19060: Ensure job token export does not throw an error

[dsasser]

Description

The CreateAdvancedQueueJob is a custom ECA Action plugin that we wrote for providing a way to send any email notification via a queue. We followed practices in ECA's own Actions that allow the primary object, in this case a Drupal\advancedqueue\Job object, to be exported as a token and therefore usable by downstream Events, Conditions, or Actions. However, as of today, the job token is not being used anywhere, and thus we weren't seeing any problems with mail delivery.

The errors we were seeing were resulting from Job object not being in an expected format (a Drupal entity, Typed Data object, or scalar value). This PR solves that by creating the token as an associative array.

Relates to #19060

Testing done

Tested by setting all ECA Models to run on every cron run (otherwise we could only test once a day, as per the configuration of the existing Models), and running cron, or running the ECA Cron service directly (ddev drush eval "\Drupal::service('eca_base.hook_handler')->cron();") which short circuits the very long running Drupal cron process.

QA steps

PRE QA steps (once per day; may already have been done today by me). We do this because the current ECA Workflows are set to trigger only once per cron at midnight and we need to be able to test them more frequently than that.

1. Visit the ECA Workflow dashboard.

2. Edit each ECA Model

3. Edit the cron Event for a given Model

4. Set the cron Event to trigger on every cron eg: * * * * *

5. Repeat for each ECA Workflow

6. Delete all existing log messages (makes reviewing easier)

As a site admin

1. Run cron via the 'VA' menu -> Run Cron
   • Validate that there are no ECA errors in the db log

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[va-cms-bot]

Cypress Accessibility Violations

/test-data-dolorum

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT
Description: Ensure buttons have discernible text
Help: Buttons must have discernible text
Nodes:

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page.">
  Impact: critical
  Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: button[data-proofing-help-title="About 'Main content' field"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

[omahane]

Ran cron and confirmed no ECA errors.

[github-actions]

Checking composer.lock changes...