Fix launcher RBAC for fully-qualified executors

[henry3260]

Why

The chart schema accepts fully-qualified executor class paths in executor, and the chart writes that value directly into Airflow config.

Airflow runtime also treats fully-qualified executor paths as valid, but the po launcher RoleBindings only matched short executor names such as CeleryExecutor and KubernetesExecutor.

As a result, valid configurations like airflow.providers.celery.executors.celery_executor.CeleryExecutor could
miss the expected scheduler or worker subjects in the generated RoleBinding,
which breaks the RBAC needed to launch pods or jobs.

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[jscheffl]

Good catch! Thanks for the fix!

I assume the change will not be able to be directly back-ported to 1.x branch but let's try...

[github-actions]

Backport successfully created: chart/v1-2x-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	chart/v1-2x-test