chore(deps): update all lvh-images main (main) (patch)

[cilium-renovate[bot]]

This PR contains the following updates:

Package	Update	Change
quay.io/lvh-images/kernel-images	patch	4.19-20240620.102250 -> 4.19-20241010.074256
quay.io/lvh-images/kernel-images	patch	5.4-20240620.102250 -> 5.4-20241010.074256
quay.io/lvh-images/kernel-images	patch	5.10-20240620.102250 -> 5.10-20241010.074256
quay.io/lvh-images/kernel-images	patch	5.15-20240620.102250 -> 5.15-20241010.074256
quay.io/lvh-images/kernel-images	patch	6.1-20240620.102250 -> 6.1-20241010.074256
quay.io/lvh-images/kernel-images	patch	6.6-20240620.102250 -> 6.6-20241010.074256
quay.io/lvh-images/kernel-images	patch	bpf-next-20240624.013140 -> bpf-next-20241021.013327

---

Configuration

📅 Schedule: Branch creation - "on monday and friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[netlify[bot]]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	a5226f666210e32c401b324ee895ff9f3bae30a0
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/67249c77f5be5a00083733bf
😎 Deploy Preview	https://deploy-preview-2615--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mtardy]

I'm rebasing now since we have 63d8f81efd05c8eee519bd955ad47e546266f6d4 in.

[tixxdz]

The PR to fix the cgroup logic on bpf-next or +6.11 kernels and the test TestCgroupv2ExecK8sHierarchyInUnified is here: https://github.com/cilium/tetragon/pull/3053

[olsajiri]

hum loader is failing now, will take a look

[cilium-renovate[bot]]

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.