[CI] Changing windows artifacts name | pushing signed files to share

[przepeck]

🛠 Summary

CVS-187402
Removing commit sha from package name to be consistent for automate.
Fixed pushing signed files to the share.

🧪 Checklist

• Unit tests added.
• The documentation updated.
• Change follows security best practices.
  ``

[Copilot]

Pull request overview

This PR updates the Windows Jenkins pipeline to make promoted artifact naming consistent (removing the commit SHA from the ZIP name) and to improve the promotion flow for signed outputs copied to the network share.

Changes:

• Persist the build timestamp as env.BUILDSTAMP and use it when promoting artifacts.
• Wrap BDBA and signing stages in catchError so failures don’t hard-fail the whole build (build becomes UNSTABLE while the stage is FAILURE).
• Add a dedicated “Promote package” stage that copies either the signed ZIP (if present) or falls back to the unsigned ZIP, and publishes it to the share under both a timestamped folder and latest.

Comments suppressed due to low confidence (1)

ci/build_test_release.groovy:168

• The signed package’s .sha256 file is only copied into the latest folder, but not into the timestamped ${destPath}\\${env.BUILDSTAMP} folder (even though the package itself is copied to both). This makes the archived buildstamp directory incomplete and breaks integrity verification for non-latest builds.

                        if (shaFile != "" && fileExists("${env.WORKSPACE}\\dist\\windows\\${shaFile}")) {
                            status = bat(returnStatus:true, script: "copy /Y \"${env.WORKSPACE}\\dist\\windows\\${shaFile}\" \"${latestPath}\\${packageName}.sha256\"")
                            if (status != 0) {