fix: Propagate serviceAnnotations to created Services

[sbernauer]

Description

Reported in https://github.com/orgs/stackabletech/discussions/57

This PR actually now uses ListenerClass.spec.serviceAnnotations...

The following ListenerClass

apiVersion: listeners.stackable.tech/v1alpha1
kind: ListenerClass
metadata:
  name: lb-with-annotations
spec:
  serviceType: LoadBalancer
  serviceAnnotations:
    # networking.gke.io/load-balancer-type: Internal
    service.beta.kubernetes.io/aws-load-balancer-internal: "true"
    service.beta.kubernetes.io/aws-load-balancer-type: internal

now produces the correct annotations on the Service

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

Preview Give feedback

1. Changes are OpenShift compatible
2. CRD changes approved
3. CRD documentation for all fields, following the style guide.
4. Helm chart can be installed and deployed operator works
5. Integration tests passed (for non trivial changes)
6. Changes need to be "offline" compatible

Reviewer

Preview Give feedback

1. Code contains useful comments
2. Code contains useful logging statements
3. (Integration-)Test cases added
4. Documentation added or updated. Follows the style guide.
5. Changelog updated
6. Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

Preview Give feedback

1. Feature Tracker has been updated
2. Proper release label has been added
3. Roadmap has been updated

[lfrancke]

Could you please include a short sentence we can use for the release notes?

[sbernauer]

ListenerClass.spec.serviceAnnotations are now correctly propagated to created Service objects.