Update mikefarah/yq Docker tag to v4.44.5

[renovate]

This PR contains the following updates:

Package	Update	Change
mikefarah/yq (source)	patch	4.44.3 -> 4.44.5

---

Release Notes

mikefarah/yq (mikefarah/yq)

v4.44.5

Compare Source

• Format comments with a gray foreground (Thanks @​gabe565)
• Fixed handling of nulls with sort_by expressions #​2164
• Force no color output when NO_COLOR env presents (Thanks @​narqo)
• Fixed array subtraction update bug #​2159
• Fixed index out of range error
• Can traverse straight from parent operator (parent.blah)
• Bumped dependencies

Note: 4.44.4 was skipped as it had a release pipeline failure

---

Configuration

📅 Schedule: Branch creation - "before 7am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[jameslamb]

/ok to test

[jameslamb]

Builds are failing for conda images, like this:

libmambapy.bindings.specs.ParseError:
Error parsing MatchSpec "python[version='>=3.11.0',3.11.*": Parentheses mismatch in "python[version='>=3.11.0',3.11.*"."

(build link)

Will look into where that's coming from.

[jameslamb]

I was able to reproduce this outside of this repo, opened a bug report: conda/conda-libmamba-solver#581

I think we're just seeing this now because there was a conda-libmamba-solver release (24.11.0) 5 days ago: https://github.com/conda/conda-libmamba-solver/releases/tag/24.11.0

[jameslamb]

/ok to test

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.