fix: Faster implementation of work queue

[godexsoft]

The new work queue implementation seems to be too slow because of its dispatcher component.
According to micro benchmark, this implementation appears to be nearly as fast as the original that did not support priorities.

[codecov]

Codecov Report

❌ Patch coverage is 95.12195% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.87%. Comparing base (e733fad) to head (95e8f78).
⚠️ Report is 2 commits behind head on develop.

Files with missing lines	Patch %	Lines
src/rpc/WorkQueue.cpp	97.14%	0 Missing and 1 partial ⚠️
src/rpc/WorkQueue.hpp	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2887   +/-   ##
========================================
  Coverage    81.86%   81.87%           
========================================
  Files          382      382           
  Lines        14506    14490   -16     
  Branches      7960     7948   -12     
========================================
- Hits         11876    11863   -13     
  Misses        1451     1451           
+ Partials      1179     1176    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kuznetsss]

[ RUN      ] WorkQueueDeathTest.ExecuteTaskAssertsWhenQueueIsEmpty
[       OK ] WorkQueueDeathTest.ExecuteTaskAssertsWhenQueueIsEmpty (124036 ms)

124 seconds for 1 test with codecov

[godexsoft]

[ RUN      ] WorkQueueDeathTest.ExecuteTaskAssertsWhenQueueIsEmpty
[       OK ] WorkQueueDeathTest.ExecuteTaskAssertsWhenQueueIsEmpty (124036 ms)

124 seconds for 1 test with codecov

That's so painful.. but i don't see a better way to implement this test since AssertMock failed us 😢

Should we consider to disable the test until better times? perhaps it's not important enough to waste 124 seconds every CI run.. we know the ASSERT will work.

[kuznetsss]

AssertMock failed us

It's WorkQueue's design, not AssertMock.

We could disable this test and create an issue to fix it later.