feat(ci): add integration tests for AutoTLS in Beekeeper workflow

[akrem-chabchoub]

Checklist

• I have read the coding guide.
• My change requires a documentation update, and I have done it.
• I have added tests to cover my changes.
• I have filled out the description and linked the related issues.

Description

• Updated the Beekeeper GitHub Actions workflow to run the CI against temporary Beelocal and Beekeeper feature branches.
• Added a second test flow targeting the local-dns-autotls cluster.
• ReRun Beekeeper checks for the AutoTLS setup (pingpong, full connectivity, retrieval and autotls checks).
• Extended the debug artifacts collection to support the new AutoTLS cluster.

Why this is needed

AutoTLS and WSS support are currently being validated on dedicated Beelocal and Beekeeper feature branches.
The existing CI only covered the standard local-dns cluster and does not exercise the AutoTLS setup.

This change allows the CI pipeline to:

• validate the AutoTLS cluster configuration,
• detect regressions in connectivity and retrieval when AutoTLS is enabled,
• and provide proper debugging artifacts when AutoTLS related checks fail.

Files changed

• .github/workflows/beekeeper.yml

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):