ci: gitlabflow workflow fixes

[jescalada]

Testing that workflows are generating release drafts for all release branches and also handling NPM publishes for multiple branches (updating old tags, identifying latest tags correctly).

Note that these changes will be reverted later to clean up the workflow files and fix the modified package.json files

[github-actions]

Thanks for the PR! The description gives good context about what you're testing with the GitLab workflow changes.

Could you please either link an existing issue (using "Fixes #N", "Closes #N", etc.) or create a new issue describing this change? According to our contributing guide, we ask that PRs reference an issue to help with tracking and discussion.

[github-actions]

🔒 Automated Security Review

Security Review Summary

✅ No security issues identified - This PR contains only CI/CD configuration changes that do not introduce security vulnerabilities.

Analysis

This pull request primarily contains GitHub Actions workflow improvements and configuration updates. The changes include:

• Addition of a new release branch drafter workflow with appropriate security hardening (step-security/harden-runner)
• Proper use of pinned action versions with commit SHashes for supply chain security
• Appropriate permission scoping (read/write permissions explicitly defined)
• Secure use of secrets.GITHUB_TOKEN and secrets.NPM_TOKEN environment variables
• Repository owner validation before Docker publishing operations
• Addition of --provenance flag to npm publish commands (improves supply chain security)

All secrets are properly referenced through GitHub's secrets mechanism, and no hardcoded credentials were found.

[jescalada]

Merging this in order to test the NPM publish flow - will revert later