Entity Share Ignore

Problem/Motivation

In a highly nested content structure with webs of entity references, it can be easy to inadvertently pull an nodes or components with entity share that you did not intend to pull. This can result in content being prematurely published before it is fully vetted and approved.

Proposed resolution

Entity Share Ignore would do the following:
Server Side:
- Entity bundles could be configured to be ignoreable. This would have the effect of creating a new boolean field for these bundles type called "field_entity_share_ignore."
- On a node-by-node (entity instance by entity instance) basis you could then mark nodes as ignored by entity share.
- This would be exposed in jsonapi, as it would be a normal field that would appear in attributes.
Client Side:
- A processor plugin called entity share ignore would implement isEntityImportable. If the entity has the field_entity_share_ignore attribute set to true, then the isEntityImportable would return false, preventing the entity from being imported. This processor plugin could be selected in remote configurations as desired.

Remaining tasks

- Create server side configuration and field creation functionality
- Create client side processor plugin
- Testing

User interface changes

N/A

API changes

A new Import processor would be available, along with the ability to easily create an entity_share_ignore field through an admin form listing all system entities/bundles.

Data model changes

New configuration schema.