[fix][broker] Align entry filter policy checks for non-persistent topics - #26774

Motivation

The topic-level entry filter endpoints in PersistentTopics check the ENTRY_FILTERS topic policy operation (READ for get, WRITE for set and remove) before handling the request. The NonPersistentTopics overrides of these endpoints skip that check, so the same operations are handled differently depending on the topic domain.

Modifications

• In NonPersistentTopics, run validateTopicPolicyOperationAsync with PolicyName.ENTRY_FILTERS before the get (READ), set (WRITE) and remove (WRITE) entry filter operations, matching PersistentTopics.
• Parameterize the entry filter tests in TopicAuthZTest to cover both persistent and non-persistent topics, and also check the get operation with applied=true.

With this change, a caller that is not permitted the ENTRY_FILTERS policy operation receives 403 Not Authorized for these non-persistent topic endpoints, as it already does for persistent topics.

Verifying this change

• Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

• TopicAuthZTest.testGetEntryFilter, testSetEntryFilter and testRemoveEntryFilter now run for both persistent and non-persistent topics.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints: non-persistent topic entry filter endpoints now check the ENTRY_FILTERS topic policy operation
• The admin CLI options
• The metrics
• Anything that affects deployment