packer: Fix installing worker RPMs in prod builds

[ondrejbudai]

We use --skip-tags rpmrepo_composer,rpmrepo_osbuild,rpmcopr for our prod
builds. Thus, if we merge the following two tasks into one, no RPMs will
be installed in prod builds, because --skip-tags joins multiple tags
with OR. (IoW a task with tags == [rpmcopy, rpmrepo_osbuild] will not
run with --skip-tags rpmrepo_osbuild).

This is quite a horrible hack, but it will hopefully unbreak us for the
time being.

[jrusz]

Depsolve errors in the Packer job:

fatal: [default]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: cannot install the best candidate for the job\n  - nothing provides osbuild-depsolve-dnf >= 116 needed by osbuild-composer-worker-108-1.20240513gitc5e6055.el9.x86_64 from composer\n  - nothing provides osbuild >= 116 needed by osbuild-composer-worker-108-1.20240513gitc5e6055.el9.x86_64 from composer\n  - nothing provides osbuild-luks2 >= 116 needed by osbuild-composer-worker-108-1.20240513gitc5e6055.el9.x86_64 from composer\n  - nothing provides osbuild-lvm2 >= 116 needed by osbuild-composer-worker-108-1.20240513gitc5e6055.el9.x86_64 from composer\n  - nothing provides osbuild-ostree >= 116 needed by osbuild-composer-worker-108-1.20240513gitc5e6055.el9.x86_64 from composer", "rc": 1, "results": []}

Sounds like some repos should be updated?

[jrusz]

It should be taking the osbuild commit SHA from Schutzfile and that was updated to v117 37995a7 so idk what's wrong

[jrusz]

I've added a commit which I believe should fix the issues we're seeing.

[croissanne]

I wonder if it isn't better to just invert the tag logic altogether #4150

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove "Stale" label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 30+7 days with no activity.