Optimize mark segments as unused

[AmatyaAvadhanula]

Currently marking segments as unused modifies used and used_status_last_updated for every segment and this can be inefficient when kill is enabled after there are a lot of accumulated unused segments. This could potentially time out as well causing KillTask failures.

This PR helps mitigate the issue by modifying only those rows which have used = true when marking them unused.

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.