Permissions given to the add-on components are too broad

[t0rr3sp3dr0]

Report

Part of #611. The current role of the HTTP Add-On is too powerful and gives read-write access to a lot of different resources in all namespaces. This same role is given to all components of the add-on even though this is not necessary.

Expected Behavior

• K8s permissions given to the add-on should be on as-needed basis.
• The permissions should be scoped based on each component needs.

Actual Behavior

• Permissions give cluster-wide read-write access to resources like ConfigMaps, Deployments, Endpoints, Pods, and Services.
• All add-on components share the same ServiceAccount, thus the same permission set.

Steps to Reproduce the Problem

N/A

Logs from KEDA HTTP operator

N/A

What version of the KEDA HTTP Add-on are you running?

0.4.0

Kubernetes Version

1.24

Platform

Microsoft Azure

Anything else?

No response