VACMS-17115: Adds ECA and friends to the platform.

[dsasser]

Description

Relates to #17115

Testing done

ECA Models can be created.

Screenshots

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

Verify ECA Works as Expected

As an administrator

1. Visit /admin/config/workflow/eca
   • Validate that there are no existing Models
2. Then click the Add New Model button
3. Provide a name and click Save
4. On the next page, under 'Add event'
   • Validate that there is an Event 'ECA cron event (ECA Base)' item
5. Select ECA cron event (ECA Base) and click 'Add Event'
6. On the subsequent page, click Save after making no changes.
7. Under the Action accordion on the next page
   • Validate there is a 'Views: Execute query (ECA Views)' action

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

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[edmund-dunn]

Worked as expected. Nice work!