Marking a resource as offline or changing labels from pipelines

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

We have to handle cases where the lockable resources can become offline for various reasons. An interesting one, is when the lockable resource is a device and the pipeline discovers that the pipeline is not working as expected. We would like to be able to mark the lockable resource as "offline";

We would also like a way for a pipeline to be able to retrieve all "offline" lockable resources, so that we can script jobs that might be able to heal or bring back a lockable resource online.

This could be achieved in many ways - my two favourites are
1. Implementing an "offline" attribute that can be set or filtered on
2. Implementing an action that would allow us to change the labels dynamically and adding the possibility to select lockable resources with a combination of include and exclude labels

My personal preference would be (2) since it may also prove useful for other cases, while an `offline` mode (1) would be very specific to my needs.

I can submit a PR for this, but before I would like feedback on the preferred option (maybe something I haven't thought of?)

### Upstream changes

_No response_