Integrate: Workspace

Problem/Motivation

The current CRM custom entities (Contacts, Relationships, and Contact Methods) are revisionable but do not support the Core Workspaces module. In a high-integrity CRM environment, performing large-scale data migrations or deduplication/merging of contacts directly on the "Live" site is high-risk. There is currently no way to stage these destructive or complex data changes in an isolated environment for review before they affect production data.

Steps to reproduce

1. Enable the Workspaces and Workspaces UI modules.
2. Switch to a non-live workspace (e.g., "Stage").
3. Create or edit a custom CRM entity (Contact).
4. Observe that the change is applied globally (or not tracked by the workspace) because the entity storage is not workspace-aware and the entity lacks the EntityPublishedInterface required for standard validation.

Proposed resolution

Integrate the CRM entities with the Workspaces module to allow for "Draft" migrations and "Staged" deduplication.

• Update @ContentEntityType annotations to include revision_metadata_keys and ensure the status key is explicitly defined.
• Implement EntityPublishedInterface on the affected entity classes. This will act as a bridge, mapping isPublished() and setPublished() to the existing status boolean field.
• Ensure the entity storage handler properly supports WorkspaceResettableInterface for clean deployment transitions.

Remaining tasks

• Update entity class definitions and annotations.
• Generate and run database updates for required revision metadata fields.
• Create a WorkspaceValidator if specific business logic is required to prevent "Dead" contacts from being pushed to Live.
• Manual testing: Perform a contact merge in a workspace and verify that the deletion of the duplicate and the update of the survivor are atomic upon "Push to Live."

User interface changes

CRM entities will now appear in the Workspaces "Manage" and "Deploy" dashboards. Users will be able to see a list of pending contact/relationship changes before pushing them to the live site. No changes to the primary CRM entity forms are expected.

API changes

Data model changes

The workspace_association table will now track revisions for contact, relationship, and contact_method entity types. No major schema changes are required for existing fields, as the entities are already revisionable.