[Bug] Core service uses 'http' port name and appProtocol when it's really https

[andrewazores]

Current Behavior

$ oc get -o yaml -n cryostat2 svc cryostat-sample
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2025-01-29T16:25:03Z"
  labels:
    app: cryostat-sample
    app.kubernetes.io/component: cryostat
    app.kubernetes.io/instance: cryostat-sample
    app.kubernetes.io/name: cryostat
    app.kubernetes.io/part-of: cryostat
    component: cryostat
  name: cryostat-sample
  namespace: cryostat2
  ownerReferences:
  - apiVersion: operator.cryostat.io/v1beta2
    blockOwnerDeletion: true
    controller: true
    kind: Cryostat
    name: cryostat-sample
    uid: 12aae064-9b0a-4f65-a6ad-799745a01794
  resourceVersion: "49355"
  uid: 686e7de9-5624-4b14-a1f9-bfe5e062570e
spec:
  clusterIP: 10.217.4.90
  clusterIPs:
  - 10.217.4.90
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - appProtocol: http
    name: http
    port: 4180
    protocol: TCP
    targetPort: 4180
  selector:
    app: cryostat-sample
    component: cryostat
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

This is with cert-manager installed and configured. The service port for 4180 should have the name and appProtocol https so that other components, like the console plugin, can correctly identify it and know what kind of requests to send.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Anything else?

No response