Backport of chore(deps): manual opencontainers/runc upgrade into release/1.11.x

[hc-github-team-nomad-core]

Backport

This PR is auto-generated from #27092 to be assessed for backporting due to the inclusion of the label backport/1.11.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@pkazmierczak
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/nomad/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Yet again, opencontainers/runc upgrade breaks compatibility, and you really have to dig into their changelogs to figure out why. From v1.3.0 on, cgroups is its own repository, and since opencontainers/runc#3999, libcontainer.Process no longer supports usernames or group names, just UID/GID.

---

Overview of commits

• 44e0bbb

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• pkazmierczak
• temp

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}