daos DAOS-15145 pool: add pool collective function

Add pool collective function to skip down and downout targets.

Required-githooks: true Features: rebuild

Before requesting gatekeeper:

[ ] Two review approvals and any prior change requests have been resolved.
[ ] Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
[ ] Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
[ ] Commit messages follows the guidelines outlined here.
[ ] Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

[ ] You are the appropriate gatekeeper to be landing the patch.
[ ] The PR has 2 reviews by people familiar with the code, including appropriate owners.
[ ] Githooks were used. If not, request that user install them and check copyright dates.
[ ] Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
[ ] All builds have passed. Check non-required builds for any new compiler warnings.
[ ] Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
[ ] If applicable, the PR has addressed any potential version compatibility issues.
[ ] Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
[ ] Extra checks if forced landing is requested
- [ ] Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
- [ ] No new NLT or valgrind warnings. Check the classic view.
- [ ] Quick-build or Quick-functional is not used.
[ ] Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

Feb 07 '24 06:02 wangdi1

Bug-tracker data: Ticket title is 'rebuild hang in nvme_recovery tests' Status is 'In Review' Labels: 'scrubbed,triaged' https://daosio.atlassian.net/browse/DAOS-15145

Feb 07 '24 06:02 github-actions[bot]

Test stage NLT on EL 8.8 completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-13764/3/testReport/

Feb 13 '24 04:02 daosbuild1

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/3/execution/node/1609/log

Feb 13 '24 12:02 daosbuild1

ping

Feb 16 '24 21:02 wangdi1

Could you add the "Features: DaosCoreTestNvme" in commit message?

sure

Feb 19 '24 22:02 wangdi1

Bug-tracker data: Ticket title is 'rebuild hang in nvme_recovery tests' Status is 'In Review' Labels: 'scrubbed,triaged' https://daosio.atlassian.net/browse/DAOS-15145

Feb 19 '24 22:02 github-actions[bot]

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/5/execution/node/1430/log

Feb 20 '24 07:02 daosbuild1

Bug-tracker data: Ticket title is 'rebuild hang in nvme_recovery tests' Status is 'In Review' Labels: 'scrubbed,triaged' https://daosio.atlassian.net/browse/DAOS-15145

Feb 21 '24 03:02 github-actions[bot]

Ticket title is 'rebuild hang in nvme_recovery tests' Status is 'In Review' Labels: 'scrubbed,triaged' https://daosio.atlassian.net/browse/DAOS-15145

Feb 23 '24 04:02 github-actions[bot]

Test stage Unit Test with memcheck on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-13764/7/display/redirect

Feb 23 '24 04:02 daosbuild1

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/8/execution/node/1173/log

Feb 23 '24 18:02 daosbuild1

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/9/execution/node/1198/log

Feb 24 '24 00:02 daosbuild1

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/11/execution/node/1401/log

Feb 27 '24 12:02 daosbuild1

Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-13764/12/testReport/

Mar 04 '24 02:03 daosbuild1

Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-13764/13/display/redirect

Mar 06 '24 19:03 daosbuild1

sigh, hardware large did not get to run due to some hardware issue.

Mar 06 '24 22:03 wangdi1

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/14/execution/node/1426/log

Mar 07 '24 21:03 daosbuild1

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/15/execution/node/1174/log

Mar 08 '24 04:03 daosbuild1

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13764/16/execution/node/1173/log

Mar 08 '24 19:03 daosbuild1

Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-13764/17/display/redirect

Mar 14 '24 02:03 daosbuild1