SqlParallel - Enable more tests. Fix compatiblity with release_time

[totten]

Overview

The unit-test CRM_Queue_QueueTest provides some generic test-coverage for a couple different backends (Sql, Memory). This expands it to also test SqlParallel.

One test case, testTimeoutRelease(), was failing when run with SqlParallel. The PR updates it to pass.

@artfulrobot I can't recall if there is a reason why SqlParallel changed the release_time filter?

Before

• In Sql and Memory-backed queues, the claimItem() logic will select items with any of these three dispositions:
  • New item, ready to go immediately (release_time=null)
  • New item, marked for future execution (release_time=NNN)
  • Previously attempted item that did not complete (eg it crashed; never finished; used up the full lease; release_time=NNN).
• In SqlParallel, claimItem() will only select items in this case:
  • New item, not previously attempted (release_time=null)

After

• In Sql, Memory, and SqlParallel, the release_time works the same way. It should support all 3 scenarios.
  • New item, ready to go immediately (release_time=null)
  • New item, marked for future execution (release_time=NNN)
  • Previously attempted item that did not complete (eg it crashed; never finished; used up the

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).