Change to F5 runners for release builds

[pdabelf5]

Proposed changes

• Change to F5 runners for release builds
• Separate release workflow
• Have e2e tests run against image built

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[Copilot]

Pull Request Overview

This PR changes the GitHub Actions runner configuration to use F5 self-hosted runners for release builds while keeping standard Ubuntu runners for pull requests. The changes split CI and release functionality, introducing a dedicated release workflow and optimizing the existing CI workflow.

• Introduces a new dedicated release workflow with F5 runners for operator releases
• Updates CI workflow to conditionally use F5 runners for non-PR builds
• Removes tag-based triggers and certification steps from the main CI workflow

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/release-operator.yml	New dedicated workflow for operator releases using F5 runners
.github/workflows/ci.yml	Updated to conditionally use F5 runners and removed release-specific functionality
.github/workflows/e2e-test.yml	Added image existence check and conditional build steps for testing

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}