BE: RBAC: Impl separate permissions for topic analysis

[bachmanity1]

Issue submitter TODO list

• I've searched for an already existing issues here
• I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

No response

Describe the feature you're interested in

Currently, any user authorized to view the topic can run the analysis. I believe this feature should be more restricted.

Describe alternatives you've considered

No response

Version you're running

8c70126

Additional context

No response

[github-actions]

Hi bachmanity1! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[Haarolean]

Currently, any user authorized to view the topic

That's not true, only ones with MESSAGES_READ permission can run the analysis. There isn't a separate permission for this, because, basically if you have permission to read messages you can achieve the same result.
Please let me know if there are any other things we should consider.

[bachmanity1]

That's not true, only ones with MESSAGES_READ permission can run the analysis.

Sorry, I meant to say read the topic, not view the topic.

if you have permission to read messages you can achieve the same result.

While this is true, I feel like access to this feature should be restricted because, for very large topics, reading all the data at once can put a heavy load on the cluster. To avoid unintentional consequences, I believe this action should be reserved only for privileged users. Besides that, looking at the code, it seems that ANALYSIS_RUN is not really used anywhere (please correct me if I'm wrong), and in my opinion, this case is an appropriate usage for it.

[Haarolean]

Sounds valid, let's proceed to your PR