Optionally disable group inheritance

What does this MR do?

This MR is introducing small changes that should show if the changes in logic are even possible to achieve without compromising performance.

This experiment aims to show the behaviour and if this is what we are looking for:

1. groups can be marked as inheritance_disabled - that means they don't inherit members from their parent.
2. this means members from ancestors groups won't be added to this group or any subproject in this group.
3. my proposition: not modeled yet: this group should not have children group to keep things easier for now.

connected to #33534 (closed)

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