Add ability to "offline" a resource through Declarative pipeline code

### What feature do you want to see added?

Currently there is no easy way to offline/reserve/unreserve a resource if it crashes through the Groovy declarative pipeline code. The subsequent builds try to use the same resource and fail. Someone has to reserve that resource manually through UI so that the other jobs do not pick the same resource. This maybe possible using the Java libraries but it is not easy to do. There should be an out of the box step like the "lock" stop to reserve, unreserve, offline resource in the declarative pipeline code.

### Upstream changes

_No response_

### Are you interested in contributing this feature?