FORCE_SPAWN will not be handled by the queue node

[rootinier]

Describe the bug

Systemv message type [3] will not be handled by queue node and the job with OPTION_FORCE_SPAWN true will not be started.

To Reproduce

1. Add job once with OPTION_INTERVAL
2. Add job once with OPTION_FORCE_SPAWN true and OPTION_RETRY -1
3. Start normal job

Expected behavior

Systemv message type [3] should be handled by queue node.

Environment

• (\TaskScheduler) Version: 3.1.0
• MongoDB Version: 3.6.14
• libmongoc Version: 1.15.2
• PHP Version 7.3.12

Additional context

[2020-06-16T11:52:59.590262+00:00] default.INFO: start job listener {"category":"TaskScheduler\\Queue"} []
2020-06-16 11:52:59 [TaskScheduler\WorkerManager,DEBUG]: spawn initial [1] workers [] []
2020-06-16 11:52:59 [TaskScheduler\WorkerManager,DEBUG]: spawn new worker [] []
2020-06-16 11:52:59 [TaskScheduler\WorkerManager,DEBUG]: spawned worker [5ee8b29bf3e7824c713aba3a] with pid [96] [] []
2020-06-16 11:52:59 [TaskScheduler\WorkerManager,DEBUG]: received systemv message type [3] [] []