Ship oscap-run-sce-script with the SCE engine

[mufeso]

Fixes #2414

The SCE engine (src/SCE/sce_engine.c, built into libopenscap_sce and packaged in the engine-sce subpackage) falls back to oscap-run-sce-script when an SCE script can't be executed, for example when /tmp is mounted noexec, as CIS and ANSSI hardening require. In openscap.spec, the helper ended up in the utils subpackage through the %{_bindir}/* glob, and engine-sce doesn't require utils, so on systems without utils every SCE check ended in error.

This PR moves %{_bindir}/oscap-run-sce-script to the engine-sce subpackage, next to its only caller, and excludes it from utils.

Testing

• rpmspec -P parses the modified spec; all subpackages are unchanged otherwise.
• Behaviour, with the project's own tests/sce/sce_xccdf.xml (rule-1000, bash_passer.sh) on a noexec tmpfs: without the helper in PATH the rule ends in error; with the helper installed it passes; in a directory that allows execution it passes without the helper.
• I searched the source tree and found no other user of oscap-run-sce-script besides sce_engine.c and the install rule in utils/CMakeLists.txt.

Notes

• maint-1.3 has the same %files entries; I'm happy to open a backport if useful.
• If you'd prefer the scanner subpackage instead, as suggested in the issue, I can change it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud