Revert "Resolve symlink path for qemu directory if possible"

[n8henrie]

This reverts commit 6b64589 (Resolve
symlink path for qemu directory if possible).

Fully resolving the symlink to qemu solves some issues for
aarch64-darwin nix with regards to finding edk2-aarch64-code.fd, but
unfortunately the fully resolved path includes the version number,
making it so that even patch updates break the path to
homebrew-installed qemu files.

Fixes #18111

Does this PR introduce a user-facing change?

Do not fully resolve symlinks in the path to `edk2-aarch64-code.fd` to prevent
breakage with qemu updates.

[Luap99]

Thanks, you need to add your sign off to the commit. And I assume you also need to add [NO NEW TESTS NEEDED] in the commit message to bypass that CI check for tests as this stuff is untested at the moment.

[n8henrie]

Thanks, you need to add your sign off to the commit.

Huh, I reviewed the PR guidelines and remembered a signature was required. It prompted for my GPG signature (which I entered), so I thought I got that part right. Will try again.

And I assume you also need to add [NO NEW TESTS NEEDED] in the commit message

Done

[n8henrie]

Ah, got it.

[Luap99]

LGTM
@baude @ashley-cui PTAL

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, n8henrie

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ashley-cui]

/lgtm
/hold

[rhatdan]

/hold cancel

[devrimbaris]

Is this deployed to 1.0.1? I still get the same error on M1 .

[Luap99]

I don't think so, lets get this into 4.5.1

/cherry-pick v4.5

[openshift-cherrypick-robot]

@Luap99: new pull request created: #18677

In response to this:

I don't think so, lets get this into 4.5.1

/cherry-pick v4.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.