Changes

HACKING: update bringup notes to account for fedora-coreos-pipeline changes

The pipeline was updated to change the structure of the jenkins images
dependency chain in [1] so we needed to update the notes here.

[1] https://github.com/coreos/fedora-coreos-pipeline/pull/1151

test-override: Build qemu in separate invocation

Fallout from [1].

[1] https://github.com/coreos/coreos-assembler/commit/18b1ec454230a8a9e76a9ea33f6d137ececc5944

jobs/test-override: disable buildah path for now

We're still ironing out issues, but we don't want to cause confusion
with Bodhi users. So for now just keep using the legacy path.

jobs/test-override: use newer API for coreos config git rev

The .config-gitrev is legacy. Let's update to use the newer API.

xref: https://github.com/coreos/coreos-assembler/pull/4282

Revert "jobs/test-override: disable buildah path for now"

Tests are passing in the buildah path for now so let's re-activate
it for streams where it is configured.

This reverts commit 7579d142427776ba5a4f8e6313d8c5dc59b99ad1.

test-override: always buildfetch

Right now we only buildfetch if we are doing autolock (i.e. basing
on mechanical streams). Let's always buildfetch so we can see an
RPM diff when the commit/container is built.

Right now there is a bug where `cosa diff` when it's the first build
in the stream will fail (i.e. causing `cosa build` to fail), but should
be fixed soon. This works around that, but also shows the RPM diff,
which is nice too.

test-override: force cosa build

We had a case where an RPM build we had fast-tracked finally got
submitted as a bodhi update and this test-override job failed
because "Input hash unchanged". i.e. it detected there was no
changes and didn't do the build, which meant the tests failed.

Let's just force the build here. We know it's not that useful
but reporting failure is worse.

jobs/bodhi-trigger: update stream_to_releasever logic

We moved the definition of the version/releasever in [1] to
build-args.conf so we need to update the logic here to source
in from that location instead of the manifest.

[1] https://github.com/coreos/fedora-coreos-config/commit/6fc060cd8a42e0e8369b9e84d67b6c400eeb863a

seed-github-ci: replace configure block with DSL API

Use the dynamic DSL branchSource{} to configure strategy,traits and
build strategies instead of patching raw XML.
This also amends traits elements from the previous static github{}.

Based on documentation from:
https://jenkins-coreos-ci.apps.ocp.fedoraproject.org/plugin/job-dsl/api-viewer/index.html#path/multibranchPipelineJob-branchSources-branchSource-source-github-traits

resolves: COS-3116 | https://redhat.atlassian.net/browse/COS-3116

cosaBuild: call `cosa osbuild` separately

In https://github.com/coreos/coreos-assembler/pull/4255 we are proposing
to remove followup target build support from `cosa build`; i.e. it won't
auto build the `qemu` target when doing a build.

Let's split this part out into a separate step here.

kolaTestIso: check for testiso command before running tests

Part of folding testiso into kola run.

kola: add --inst-insecure flag to kola tests

Autodetection of dev builds fails on builds where 'dev' is not part of
the filename scheme, like 'rhcos-9.8.20260506-0-live-iso.x86_64.iso'.
This causes kola tests to fail when they should run in insecure mode.

The obsolete 'vars/kolaTestIso.groovy' used the insecure
flag by default, so this restores that behavior explicitly.

cosaPod: add timeout to prevent pods from running indefinitely

Add a timeout parameter (default 24 hours) to cosaPod to prevent
hung or failed pods from blocking the pipeline. Callers can override
the default by passing timeout (in hours), or disable it with
timeout: 0 for jobs like debug pods that may need extended runtime.

Fixes: https://github.com/coreos/fedora-coreos-pipeline/issues/1296

kola: make testiso command detection more verbose

There is a strange issue where probably `shwrapRc("kola help | grep -q testiso")`
returns a non-zero exit code despite the `testiso` command being available.
As a result, we incorrectly fall back to the newer code path and hit
failures like:

  06:19:32  Error: unknown flag: --inst-insecure