fix: Don't fail on Alpine checksums for Security releases

[nschonni]

Description

Added back the recent "skip" concept for the Apline checksums falling over, but still allow Alpine to try and update itself if the checksum is available.

Motivation and Context

Testing Details

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[MikeMcC399]

@nschonni

We've overlapped again! So I'll put my help text PR #2420 into draft state.

[nschonni]

I've updated the help text after seeing yours

[nschonni]

I didn't check what happens to the automation after a partial version update without the Alpine builds lands here? Will it still pick up the partial/continue with a new PR (with a colliding PR name)

[MikeMcC399]

It seems this would be related to issue #2363 and to the attempts to decouple security releases from musl builds submitted by:

• @ItsHarta in Decouple security releases from MUSL builds #2353
• @bmuenzenmeyer in attempt to separate security releases from experimental musl releases #2348

both of the PRs have stalled.

Also #2424 from @RafaelGSS says there's a security release planned on 2026-03-24, in one week, so it looks like there is an urgent need to get some of this sorted out in case there is a delay in musl builds on Tuesday next week.