Use sharding for Kuadrants Authorino deployment

Currently, the Authorino deployed by Kuadrant is configured as cluster-wide and without sharding, which means it will reconcile all AuthConfigs on the cluster, which means you cannot use standalone authorino deployments on the same cluster as everything will be also reconciled by the Kuadrant Authorino.

Solution would be to deploy Kuadrant Authorino with sharding to some label like `kuadrant.io/managed=true` and add the same label to AuthConfigs generated from AuthPolicy

Read the Kuadrant Authorino deployment configuration and trace how AuthPolicies generate AuthConfigs. Confirm how Authorino sharding can target the kuadrant.io/managed=true label, then verify generated AuthConfigs receive that label so standalone Authorino deployments do not reconcile them.

Written by the indexing model from the issue text.