[Feature]: Update the label strategy to the latest version

[lwpk110]

Summary 💡

The current labeling strategy applied by the operator needs to be updated to align with the latest operator recommendations. The existing labels :

• "app.kubernetes.io/Name" - custom resource instance name
• "app.kubernetes.io/component" - role name
• "app.kubernetes.io/managed-by" - operator name

need to be replaced by :

• "app.kubernetes.io/name" - server name
• "app.kubernetes.io/instance" - custome resource instance name
• "app.kubernetes.io/managed-by" - develop group name

and a new label "app.kubernetes.io/role-group" (role group name) added.

Examples 🌈

For a resource instance "trinocluster-sample" of role "coordinator" managed by group "trino.zncdata.dev", the labels would change from:

• "app.kubernetes.io/Name: trinocluster-sample"
• "app.kubernetes.io/component: coordinator"
• "app.kubernetes.io/managed-by: trino-operator"

To:

• "app.kubernetes.io/name: trino"
• "app.kubernetes.io/instance: trinocluster-sample"
• "app.kubernetes.io/managed-by: trino.zncdata.dev"
• "app.kubernetes.io/role-group: default"

Motivation 🔦

Updating to the current labeling recommendations allows resources to be more easily discovered, managed and automated according to Kubernetes upstream practices. This ensures the operator's labels are aligned with evolving industry standards.