Look for scoped_packages in the build group, not the SRPM group

[NeilHanlon]

Is this feature request related to a problem? If so, please describe it.

The options we are applying in terms of enabling/disabling modules as well as including additional packages (SCLs) are actually applied to the build workflow, not the srpm workflow, and we should make it clear and reduce confusion by only accepting the arguments inside the build block

Describe the solution you'd like to see

Move the scoped_package{} configs into the build section, and add messaging similar to #85 to alert user.

Have you considered alternative solutions/features? If so, please describe them.

No response

Version and Build Information

n/a

Additional Context

No response