Incorrect labels in Chart v0.13.1 - extra Listener pods

[chrede88]

Checks

• I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• I am using charts that are officially provided

Controller Version

0.13.1

Deployment Method

Helm

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions).
• I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

1. Update charts to v0.31.1
2. Notice extra Listener pod and incorrect labels (still referring to 0.13.0)

Describe the bug

The most recent version of the action runner charts apply incorrect labels - still referring to 0.13.0, instead of 0.13.1.
This results in the controller not removing the old AutoscalingListener when creating the new one. As a result, two listener pods are scheduled and conflicting.

If the old AutoscalingListener is removed the issue is resolved, but all resources still have the wrong version labels.

Here is the current yaml manifest as per my cluster (running v0.13.1):

apiVersion: actions.github.com/v1alpha1
kind: AutoscalingListener
metadata:
  labels:
    app.kubernetes.io/part-of: gha-runner-scale-set
    app.kubernetes.io/version: 0.13.0
    helm.sh/chart: gha-rs-0.13.0_8c7de2bc84e9
spec:
  image: ghcr.io/actions/gha-runner-scale-set-controller:0.13.1

Describe the expected behavior

Correct version labels are applied to the resources.

Additional Context

N.A.

Controller Logs

N.A.

Runner Pod Logs

N.A.