obs-runner: Disabled architectures on a OBS package get re-enabled when CI creates a branch

Affected images versions

• not relevant, CI issue

Steps to reproduce

• Pick a package with some architectures disabled on OBS, like cross-toolchain-base
• Create a new MR for it

Expected result

• The architectures disabled in the original OBS package should be disabled in the branched OBS package too
• The pipeline in the MR should only have obs monitoring jobs for the architectures enabled in the original package

Actual result

• All the architectures get re-enabled, causing the pipeline to fail
• Disabling the architecture manually on the branched package and re-triggering the pipeline make things work as intended

Reproducibility

Always

Impact of bug

The contribution workflow is broken for packages with disabled architectures. This happens relatively often for downstreams where many package only build on selected architectures.

Root cause

It seems to be just how the OBS API works right now.

Outcomes

MRs to manually copy the build meta from origin to branch:

https://github.com/collabora/open-build-service-rs/pull/25 https://github.com/collabora/obs-gitlab-runner/pull/44

This maybe would be better fixed in upstream OBS instead of the gitlab runner

Management data

This section is for management only, it should be the last one in the description.

/cc @ritesh @em @refi64 @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9966