DAOS-16650 control: dmg system exclude, update group version (#15288)

[kccain]

With this change, when a daos administrator runs dmg system exclude for a given set of engines, the system map version / cart primary group version will be updated. In turn, daos_engines will more immediately detect the "loss" of the administratively excluded engines, update pool maps and perform rebuild. This change supports a use case of a proactive exclusion of ranks that are expected to be impacted by planned maintenance that would cut off connectivity to certain engines.

skip-nlt: true
Features: control ms_membership

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.

[github-actions]

Ticket title is 'DAOS 2.6.0 : 128 Node cluster, when user tried to start the few stopped engines, Different engine got crashed.'
Status is 'Awaiting backport'
Labels: 'ALCF'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-16650

[kccain]

In Jenkins build 1, the NLT "new warnings" failure is actually an instance of this known bug https://daosio.atlassian.net/browse/DAOS-16716

So I force-pushed a change to the PR to specify skip-nlt: true in the commit pragmas to get more testing done on this change.

[kccain]

In Jenkins build 1, the NLT "new warnings" failure is actually an instance of this known bug https://daosio.atlassian.net/browse/DAOS-16716

So I force-pushed a change to the PR to specify skip-nlt: true in the commit pragmas to get more testing done on this change.

@daos-stack/daos-gatekeeper build 2 passed testing (minus NLT as noted due to DAOS-16716). Requesting a force landing. However, if you would prefer me merging latest release/2.6 branch (that very recently got a fix for that bug), I can do that and push for a final round of CI testing.