test/simplified-installer: fix yq installation on rhel8

[runcom]

Basically pulls in kislyuk/yq#165 to fix the installation issue

This pull request includes:

• adequate testing for the new functionality or fixed issue
• adequate documentation informing people about the change such as
  • submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

[bcl]

Could you make the commit message a bit more verbose, explain why it needs to be pinned?

[runcom]

Basically pulls in kislyuk/yq#165 to fix the installation issue

forgot to add this to the commit message

[runcom]

not sure what's happening with the c9s test (cc @henrywang)

[runcom]

this is still needed to avoid breakages in the future by pinning version - notice main PRs are now passing as they're getting the new version from pip

[bcl]

not sure what's happening with the c9s test

There was a problem with gpg2 defaults that was reverted, but doesn't seem to have made it into whatever packit uses to run things. https://bugzilla.redhat.com/show_bug.cgi?id=2070722

[yih-redhat]

The failure on cs9 is because the fdouser was not created when ansible try to run check with fdouser, then I logon the target vm, and found that the fdouser is created after a few minutes.

1. Ansible runs at [2023-04-10T23:01:42-04:00]
2. foduser was created at Apr 10 23:03:30 (about two minutes later)

I'm not sure why it's taking longer than before to create this fdouser on cs9, but I will add a check in script to wait for this user to present.

[bcl]

The failure on cs9 is because the fdouser was not created when ansible try to run check with fdouser,

Take a look at the logs, it's filled with entries like:

Public key for glibc-minimal-langpack-2.34-61.el9.x86_64.rpm is not installed. Failing package is: glibc-minimal-langpack-2.34-61.el9.x86_64
 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-Official

So I would bet that's causing other strange problems.