Plugin config: Delete entity along with GroupContent

Here is a patch for group 2 and 3...

The patch in #15 is working for our website as we do not allow sharing content between groups.

Anyway, the proposed solution, is good when:

• Content is not shared at all
• Content is shared between same group type
• Their is no conflict in the delete settings -for the same relation plugin- in the multiple group types

But, I wonder what should happen in case an entity is shared between 2 groups of different group type; where the relation plugins in each group type has different settings for entity deletion. For example:

• Having group type A and group type B
• Enable the relation plugin for Page content type in both A and B group types
• In group type A: The configs for the plugin is > "Delete target entity when group relation is deleted" (So we always want to delete - No matter if the entity is being shared or not.)
• In group type B: We keep the default > Do not delete the entity (The option do delete the target entity is not selected).
• Create 2 groups: Group X of type A and Group Y of type B
• Create a page node in group X and share it with group Y
• 1. If the user deleted the relation in group X, the node will be deleted
• 2. If the user deleted the relation in group Y, the node won't be deleted

Case #1:
It is deleting an entity that is being shared with other group (of different type) that assumes an entity should not be deleted when deleting its relation.

I think we should have a third option e.g. "Only delete when all same relation plugins in other group type allow to delete".
When this option is selected, Case #1 won't delete the target entity as it is being shared with a group of another type that prevents deleting the target entities!

Here's a version of the patch for Group 1.0.x (tested on 1.6.0) that combines the patch from #12 with the patch from #3 of this issue: https://www.drupal.org/node/3364703 →

The two are unrelated, but since they touch the same code, you can't apply both at once. This is likely something that only a few people would run into and probably frowned upon by maintainers, but uploading anyways. All this does differently from #12 is reload the entity in order to check that it still exists before saving. Strangely the code comments around line 216 of GroupContent.php imply that this is already happening, but it's clearly not.

s_leu → changed the visibility of the branch 2754399_2872697_2.x_combined to hidden.

s_leu → changed the visibility of the branch 2754399_2872697_2.x_combined to active.

s_leu → changed the visibility of the branch 2754399_2872697_2.x_combined to hidden.

s_leu → changed the visibility of the branch 2754399_2872697_2.x_combined to hidden.

The $entity->delete() revealed that we're missing to install the users_data table, this failed in a custom test that was extended GroupKernelTestBase, so adding an install_schema() call to fix that.

Also there's a hidden branch with changes that combine these here with the ones for 🐛 Node update hook is triggered upon group content create Needs work comment #54 🐛 Node update hook is triggered upon group content create Needs work in case someone needs this too.