chore(deps): update dependency trivy

[renovate]

This PR contains the following updates:

Package	Update	Change
trivy	patch	0.70.0-3.azl3 → 0.70.0-4.azl3
trivy	patch	0.70.0-ubuntu24.04u3 → 0.70.0-ubuntu24.04u4
trivy	patch	0.70.0-ubuntu22.04u3 → 0.70.0-ubuntu22.04u4
trivy	patch	0.70.0-ubuntu20.04u3 → 0.70.0-ubuntu20.04u4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 these updates again.

---

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

---

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

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168659191
Failed job/stage/task: Run AgentBaker E2E
First failing step/test: NetworkIsolated cluster reuse of abe2e-azure-networkisolated-v3-d6cc9

RCA: This is the recurring NetworkIsolated shared-cluster cleanup flake. E2E found existing cluster �be2e-azure-networkisolated-v3-d6cc9 already Failed/Deleting and failed before PR-specific scenario validation. Prior evidence for this same cluster shows ResourceGroupDeletionBlocked / InUseNetworkSecurityGroupCannotBeDeleted on �be2e-networkisolated-securityGroup still attached to the shared VNET subnet.

Confidence: High. Corroborated by timeline/status, Run AgentBaker E2E log 538, unrelated PRs hitting the same cluster/signature, and the existing repair item #38506740.

Strongest alternative: the trivy Renovate payload caused image/build behavior; less likely because the primary E2E failure is the same stale shared cluster signature across unrelated PRs.

Recommended owner/action: AgentBaker E2E test-infra owner: clean/quarantine �be2e-azure-networkisolated-v3-d6cc9, remove the stuck NSG/subnet association, and harden shared-cluster cleanup/retry.

Wiki signature:
etworkisolated-shared-cluster-delete-blocked-inuse-nsg (source of truth)