DAOS-13117 chk: properly set pool label in check report upcall

[Nasf-Fan]

The cpr->cpr_label is empty for orphan pool, that will confuse related MS logic when handle the check report upcall. So under such case, we should use PS pool label in the check report upcall.

The patch also fixes another issue when handle broken pool without pool service quorum. For such case, it uses ds_chk_regpool_upcall() to notify MS to refresh related pool service replicas. But at that time, we do not know whether related pool label (between MS and PS) is consistent or not. Under such case, we should use MS pool label instead of PS label to avoid over-writting MS pool label by wrong.

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 watchers.
• 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.

[github-actions]

Bug-tracker data:
Ticket title is 'Properly set the pool label in check report upcall for repairing orphan pool'
Status is 'In Progress'
https://daosio.atlassian.net/browse/DAOS-13117

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

Test stage Build on Leap 15.4 with Intel-C and TARGET_PREFIX completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-11896/1/execution/node/503/log

[daosbuild1]

Test stage Build on Leap 15.4 with Intel-C and TARGET_PREFIX completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-11896/2/execution/node/412/log

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

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

[Nasf-Fan]

rebuild simple failed for DAOS-12244, not related with the patch.