feat(kuma-cp): added configuration of plugins and its order

[lukidzi]

Added possibility to configure which plugins should be applied and their order. Not sure yet how to test it properly.

• Link to docs PR or issue --
• Link to UI issue or PR --
• Is the issue worked on linked? -- fix: Controllable plugin ordering #5441
• The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) --
• The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Unit Tests --
• E2E Tests --
• Manual Universal Tests --
• Manual Kubernetes Tests --
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

[lahabana]

Looks cool! I guess one thing here is that disabled policies still have an API for resource which is a little strange. Also you should update the readme on the policy gen

[lukidzi]

Looks cool! I guess one thing here is that disabled policies still have an API for resource which is a little strange. Also you should update the readme on the policy gen

Do you think we should filter on matching to dp/api and do not allow the creation of other policies? More like really disabling those plugins? It seems to be difficult because most of the API things we generate before and even if we do not load the plugin API is going to show specific configuration.

[lahabana]

LGTM but you likely need to update wiht policies that were recently added