[BEAM-13666] Stuck inventory jobs should be cancelled and rescheduled for next run

[elink21]

As Valentyn mentioned on the Jira Ticket, if a worker is marked as temporarily offline and an Inventory job started during that process, then the job is going to stuck and it's necessary to cancel it manually and run it again later, even if the worker is back online it can not retake the job.

The reason behind that was the eligibility option set in the code, Eligibility options , by changing it to all nodes the job will continue it's execution after the worker is online again.

This change doesn't affect the stablished workers-job mapping, as the allowed nodes and default node options are already set.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[asf-ci]

Can one of the admins verify this patch?

[asf-ci]

Can one of the admins verify this patch?

[tvalentyn]

Thank you!