Add DESCRIBE permission by default for consumer groups in ACL service

[polegkashti]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
I modified the ACL service to automatically include the DESCRIBE permission when creating an ACL for consumer groups. This ensures that consumer groups have both READ and DESCRIBE permissions by default, preventing common authorization errors that occur when only READ is assigned.

This change addresses the issue where users frequently encounter "Group authorization denied" errors and have to manually add a DESCRIBE ACL. With this fix, the ACLs are more functional out of the box.
Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[Haarolean]

@polegkashti PTAL at the build, there are a few tests failing

[polegkashti]

@polegkashti PTAL at the build, there are a few tests failing

I fixed it; the issue was caused because the tests didn't expect the DESCRIBE ACL for consumer groups :)