fix: support jq 1.6 when building release manifests

[Luca Forstner (lforst)]

Release manifest generation fails on jq 1.6 because $label is parsed as a reserved keyword, producing syntax error, unexpected label and exit code 3.
This blocked bt's v0.22.0 release plan.

Rename the jq variable to $package_label in the shared manifest template while preserving the label JSON field and all action inputs.
Regenerate the standalone manifest action and the JavaScript, Python, and Ruby configure actions.
Bump the release action family to 1.0.1; the other generated action changes only update that version stamp.

Validation:

• mise exec -- rake ci passed, including action/workflow schemas and generated-output drift checks.
• Reproduced the original jq 1.6 syntax error and confirmed the renamed variable succeeds.
• Executed the generated manifest step from all four affected actions on jq 1.6 and 1.7.1, asserting JSON output for empty input, an npm package with quotes/newlines in its label, and multiple registries with published-state flags (24 cases passed).