yq: failed traversing anchors in version.yaml

[Pennyzct]

Description of problem

Recently, initrd-related CI are failing frequently.
http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-18-04-PR-initrd/2843/

INFO: Image to generate: kata-containers-*default-initrd-name-*default-initrd-version-osbuilder-7526f49-agent-36b37f6.initrd
......
./rootfs-builder/rootfs.sh: line 280: /tmp/jenkins/workspace/kata-containers-runtime-ubuntu-18-04-PR-initrd/go/src/github.com/kata-containers/osbuilder/rootfs-builder/*default-initrd-name/config.sh: No such file or directory
Failed at 120: sudo -E AGENT_INIT="${AGENT_INIT}" AGENT_VERSION="${agent_commit}" GOPATH="$GOPATH" USE_DOCKER=true OS_VERSION=${os_version} ./rootfs-builder/rootfs.sh "${distro}"
Failed at 26: "${cidir}/install_kata_image.sh" "${tag}"

Debugging on the above output, the cause may come from that yq failed reading values from assets.initrd.architecture.$arch.name
Based on the latest yq spec, the read command could print out the anchors of a document and can also traverse them.
But when anchor refers to an scalar (string, integer etc), the latest yq could not traverse it.
e.g.

$ yq read versions.yaml "assets.initrd.architecture.ppc64le.name"
*default-initrd-name

[Pennyzct]

/test

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@a91cb13). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2431   +/-   ##
=========================================
  Coverage          ?   50.88%           
=========================================
  Files             ?      112           
  Lines             ?    16157           
  Branches          ?        0           
=========================================
  Hits              ?     8222           
  Misses            ?     6922           
  Partials          ?     1013

[Pennyzct]

/test

[Pennyzct]

Hi~ @grahamwhaley
I've also done a few research on the new yq anchors and alias. Like I said above

when anchor refers to an scalar (string, integer etc), the latest yq could not traverse it.

But it's okay with the collection(sequence, map, etc), so here, I refine all the anchors in version.yaml to refer to collection, not scalar.
I'll raised an issue in yq community to see if my understanding is correct~~~

[Pennyzct]

About ARM CI failure, I've already raised another PR #2435 to fix it. ;).

[amshinde]

@grahamwhaley Can you take a look?

[Pennyzct]

Hi~ guys
Thanks for @jodh-intel raising an issue in yq community for this traversing anchors problem.
We already got answer from them and @jodh-intel has already raised an issue kata-containers/tests#2290 to try to fix them. ;).
So I will close this PR here~~~