[BUG] `OSpackage.sh` Script Should Not Attempt to Decompose Repository-Defined RPM-Lists When Invoking The Full `yum install`

Describe the bug

OSpackages.sh is intended to allow installation from either a yum repository-defined RPM package-group or a manifest file. Presumably, at some point, the package-group logic got changed so that, instead of directly referencing the package-group by name, the full yum install logic uses a list of RPMs generated by decomposing the repository-defined RPM package-group into its constituent RPMs. While the two methods should be equivalent, they may not be if a given distro has poor dependency-resolution and makes use of other-than-core package-groups more difficult/error-prone than it needs to be (see #98). Also makes seeking support from a vendor or repository-owner more difficult when errors are encountered in the overall build-process

Expected behavior

When checking the build-logs, one should see a yum install @<GROUP_NAME> installation-method being invoked, not yum install RPM1 RPM2 … RPMn (if not using the -m flag to pass a manually-composed RPM-manifest file).

Deviance Description

All builds currently take the form of yum install RPM1 RPM2 … RPMn , regardless of whether using repository-defined RPM-groups or RPM-manifest files.

Start in OSpackages.sh and trace how repository-defined RPM groups are handled when the -m flag is not used. Check the build logs to confirm the current yum install form, then verify that group-based installs retain the @<GROUP_NAME> reference while manifest-file installs remain unchanged.