WHAT

Implement feature gate for topic config policy, so that it won't be blocked by or block other components

WHY

it won't be blocked by or block other components

HOW

<Suggestions for how this may be solved.> [Optional]

DONE

Have a feature flag to enable/disable the new topic config policy

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged