Consul client pods by scraping annotations are not valid for TLS in Helm chart

[SrivatsaSrinivas]

Description:
Issue Description:
Currently, the Helm chart for Consul client daemonset lacks proper prometheus annotations to enable metrics scraping if tls is enabled. This functionality is crucial for scraping metrics from Consul clients within a Kubernetes cluster.
https://github.com/hashicorp/consul-k8s/blob/main/charts/consul/templates/client-daemonset.yaml#L91C6-L100C19
Expected Behaviour:
Consul client pods should be able to automatically scrape metrics from 8501 port and with "https" scheme if TLS settings is enabled.

Steps to Reproduce:

Deploy Consul client pods with TLS enabled using the current Helm chart.

Notice that the prometheus scrape annotations are pointed to "8500" port and uses "http" scheme even if TLS is enabled.

Proposed Solution:

Modify the Helm chart to include check for TLS and configure scraping annotation based on that.(similar to consul server statefulset helm configuration)
https://github.com/hashicorp/consul-k8s/blob/main/charts/consul/templates/server-statefulset.yaml#L134C9-L147C19

Environment Details:

Kubernetes version: EKS 1.25
Helm version: 1.2.3
Consul version: 1.16.3