fix case where OneTimeJob with concurrent limit and limited runs fails to run

[JohnRoesler]

What does this do?

Moves the check for WithLimitedRuns to the new job completed channel instead of having it on the scheduling channel. Currently there is an interesting bug highlighted in #691.

What's actually happening now this case you provided, is that the job is being sent to the wait mode limiter and before it has a chance to run, it's being removed by the scheduler because it thinks the job has run already and reached it's limit.

Which issue(s) does this PR fix/relate to?

resolves #691

List any changes that modify/break current functionality

Have you included tests for your changes?

✅

Did you document any new/modified functionality?

• Updated example_test.go
• Updated README.md

Notes