Draft: Multi groups

What does this MR do?

Proof of concept to use multiple-groups to back optional group inheritance.

Pibling refers to a collective term (of dubious origin) for aunt/uncle, which is a parental sibling, or "pibling". Nibling is the inverse of pibling. It's a collective term for niece/nephew. I'm happy to receive name improvements!

graph TD;
  rootA -- parent-child --> childA;
  rootA -- parent-child --> childB;
  childA -. shared .-> childB;
  rootA -. pibling-nibling .-> rootB;

• parent-child : Namespace#parent_id
• shared : GroupGroupLink
• public-nibling : Namespace#pibling_id

This should all end up in a many-to-many join model eventually.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team