Release SBR v0.1.0 Tech Preview

Consider using  Konflux User Advisor Google NotebookLM (see email) for all the threads in #konflux-users channel, and it could help us troubleshoot errors and ideas faster without waiting for a Konflux support folks.

Acceptance Criteria:

1. Set the ticket status as Release Pending when all the child tasks are done before GA
2. The GA ticket and release were completed
3. (optional) Update our retrospective (if there is any)
4. Update our Support Matrix: https://access.redhat.com/support/policy/updates/openshift_operators
5. Close any related tickets with the release and release the release, e.g., go to rhwa-25.4 and click on Release
6. Set the ticket status as Closed and close the ticket

Related Tasks:

1. Add git tag upstream, make a release and git tag downstream.
2. CI First - Setup OCP CI for release branch upstream (medik8s directory)
   1. Copy the main config file (e.g., for NMO see medik8s-node-maintenance-operator-main.yaml) to a new release config file, and update its branch name (e.g., NMO branch from here).
   2. Run make update to create presubmits file and push the PR (e.g., see NMO presubmits file to release-4.12 branch).
3. Upstream First - 
   1. Release upstream before downstream GA
   2. Consider releasing the upstream version to the Community Catalogs (publish it in OperatorHub and OKD).

Resources:

• https://konflux-ci.dev/docs/advanced-how-tos/building-olm/
• Old Release Tasks with CPaaS - https://spaces.redhat.com/display/dragonfly/New+Release+Tasks 
• https://docs.engineering.redhat.com/display/CFC/Best_Practices
• Jira-related issues - https://issues.redhat.com/servicedesk/customer/portal/2