Exercise oneTBB preview feature of supporting limited resources

[knoepfel]

This PR exercises the proposed features described at uxlfoundation/oneTBB#1964.

Because our CI container does not yet include a build with the proposed software, I attach printouts showing successful executions of each test case:

• serialize_functions_based_on_resource.txt
• serialize_functions_in_diamond_graph.txt
• test_based_on_onetbb_pr_1677.txt

This PR also removes the phlex/graph subdirectory and its own support for limited resources, in favor of the oneTBB implementation.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@            Coverage Diff             @@
##             main     #366      +/-   ##
==========================================
- Coverage   85.36%   85.20%   -0.17%     
==========================================
  Files         122      119       -3     
  Lines        2433     2399      -34     
  Branches      389      387       -2     
==========================================
- Hits         2077     2044      -33     
+ Misses        233      232       -1     
  Partials      123      123              

Flag	Coverage Δ
unittests	85.20% <ø> (-0.17%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f1dd203...1275090. Read the comment docs.

🚀 New features to boost your workflow:

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

[marcpaterno]

I think this testing is sufficient. I am not at all sure how to test that the implementation achieves the goals of "fairness", etc. Perhaps we should discuss the feasibility of unit- or integration-tests of such things with the oneTBB team members?

[knoepfel]

I think this testing is sufficient. I am not at all sure how to test that the implementation achieves the goals of "fairness", etc. Perhaps we should discuss the feasibility of unit- or integration-tests of such things with the oneTBB team members?

Thanks, @marcpaterno. See #378.