Add updateLock pipeline step for resource management

[mPokornyETM]

Summary

This PR adds a new \updateLock\ pipeline step that allows pipelines to dynamically manage lockable resources without using the Jenkins UI.

Features

• Create resources: \updateLock(resource: 'name', createResource: true)\
• Delete resources: \updateLock(resource: 'name', deleteResource: true)\
• Set labels (replace all): \updateLock(resource: 'name', setLabels: 'label1 label2')\
• Add/remove labels: \updateLock(resource: 'name', addLabels: 'new', removeLabels: 'old')\
• Set note: \updateLock(resource: 'name', setNote: 'Updated by pipeline')\

Example Usage

\\groovy
pipeline {
agent any
stages {
stage('Setup') {
steps {
// Create a resource if it doesn't exist
updateLock(resource: 'my-resource', createResource: true, setLabels: 'env-test')
}
}
stage('Use') {
steps {
lock('my-resource') {
echo 'Using the resource'
}
}
}
stage('Cleanup') {
steps {
// Optionally delete the resource
updateLock(resource: 'my-resource', deleteResource: true)
}
}
}
}
\\

Validation

• setLabels cannot be combined with addLabels or removeLabels
• deleteResource cannot be combined with createResource or any modification options
• Resources cannot be deleted while locked, queued, or reserved

Prior Art

This is a fresh implementation based on the original design from PR #305 by @gaspardpetit, which became stale after 4+ years. Closes #305.

---

Testing

Automated Tests

• 15 new tests in \UpdateLockStepTest.java\ covering all functionality
• All tests passing: \mvn test -Dtest=UpdateLockStepTest\

Manual Testing Steps

\\�ash
mvn hpi:run
\
Then in Jenkins:

1. Create a Pipeline job
2. Use the example script above
3. Verify resources appear/disappear in Manage Jenkins → Lockable Resources
4. Test label modifications show correctly in the UI
5. Test that deleting a locked resource fails with appropriate error

Performance Impact

• Minimal: Step runs outside hot paths
• Uses existing \LockableResourcesManager\ synchronization patterns
• Single \save()\ call per execution (same as existing steps)
• No new background threads or scheduled tasks

[mPokornyETM]

I can confirm that ma locale developer tests (on windows with Java 25) are OK

[github-actions]

⚠️ Auto-merge countdown: This PR will be auto-approved in 1 day(s) if no review is submitted.

[github-actions]

⏸️ Auto-merge countdown PAUSED: CI checks are not passing. The countdown will resume when all checks are green.

[github-actions]

✅ Auto-approved: No review received within 3 days. Merging now.

[github-actions]

Auto-approved: no review received within 3 days of opening.