release-25.2: release: fix redhat preflight component ID

[rail]

Backport 1/1 commits from #158064 on behalf of @rail.

---

Previously, the publish script was using PFLT_CERTIFICATION_PROJECT_ID to set the Red Hat preflight component ID, but it should be using PFLT_CERTIFICATION_COMPONENT_ID instead. This change corrects that environment variable to ensure proper functionality when publishing Red Hat releases.

See
redhat-openshift-ecosystem/openshift-preflight#1318 for the details.

Epic: none
Release note: none

---

Release justification: release automation changes

[blathers-crl]

Thanks for opening a backport.

Before merging, please confirm that it falls into one of the following categories (select one):

• Non-production code changes. Includes test-only changes, build system changes, etc.
• Fixes for serious issues. Defined in the policy as correctness, stability, or security issues, data corruption/loss, significant performance regressions, breaking working and widely used functionality, or an inability to detect and debug production issues.
• Other approved changes. These changes must be gated behind a disabled-by-default feature flag unless there is a strong justification not to.

Add a brief release justification to the PR description explaining your selection.

Also, confirm that the change does not break backward compatibility and complies with all aspects of the backport policy.

All backports must be reviewed by the TL and EM for the owning area.

[blathers-crl]

✅ PR #158069 is compliant with backport policy

Confidence: high
Backward compatible: true
Explanation: The pull request changes a file (publish-redhat-release.sh) located within a path designated for build and CI operations (build/teamcity/). As specified in the CockroachDB backport policy, changes to non-production files such as build scripts and CI configurations do not require a critical bug justification or feature flag gating. Furthermore, the PR provides a 'Release justification: release automation changes,' which is sufficient for an exception from the standard backport policy requirements even if the changes were production-related. Given that the file falls under the approved non-production file patterns and a release justification is present, the PR is compliant.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is