Limit Renovate Alpine updates to 3.22.x series

[Copilot]

• Rebase PR on main branch
• Remove revert part (Alpine already at 3.22.2 in main)
• Keep only renovate.json packageRule changes
• Use regex pattern /^3\.22\./ to allow patch updates

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[DavidePrincipi]

@copilot rebase this PR on main, removing the revert part as needed

[Copilot]

@copilot rebase this PR on main, removing the revert part as needed

I've rebased the PR on main and removed the revert changes (since main already has Alpine 3.22.2). The branch now contains only the renovate.json packageRule to limit Alpine updates to 3.22.x.

However, I cannot force-push the rebased branch due to divergent histories. The new commit (d3c0f957) is ready on the local copilot/sub-pr-1045 branch based on main, but pushing requires force-push which I cannot perform automatically.

Could you either:

1. Manually force-push this branch, or
2. Let me know if you'd like me to create a new PR with a different branch name?

The changes are ready and only include the renovate.json packageRule modification.