Fix: headless svc for all roles as connection requires

[Maleware]

Description

This PR adds -headless service to all airflow roles

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

• Changes are OpenShift compatible
• CRD changes approved
• CRD documentation for all fields, following the style guide.
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Changes need to be "offline" compatible
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

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

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[Maleware]

Part of stackabletech/issues#692

[Techassi]

I feel like there should be a release note for this either here or over at stackabletech/issues#692.

CC @adwk67, @Maleware

[Maleware]

Release Notes

Airflow: Listener Service for airflow on role group level, for webserver role only. Internal communication via `-headless` service.

[lfrancke]

@Maleware I'm afraid those release notes read more like a changelog. I don't understand them I'm afraid. Can you try rephrasing it again to be a bit more descriptive?

[Maleware]

Sorry, overlooked.

Airflow: Adds a listener service per role group on the `Webserver` role to access Airflow UI. Internal communication to e.g. `executers` will be handled via a exclusively cluster internal `-headless` service.  Metrics are additionally exposed internal only, with a `-metrics` service.