DAOS-15589 test: Re-enable skipped tests

[saurabhtandan]

Re-enable skipped tests
PoolListConsolidationTest.test_lost_majority_ps_replicas PoolListConsolidationTest.test_lost_all_rdb
PoolMembershipTest.test_orphan_pool_shard
PoolMembershipTest.test_dangling_pool_map
PoolMembershipTest.test_dangling_rank_entry

Test-tag: test_lost_majority_ps_replicas test_lost_all_rdb test_orphan_pool_shard test_dangling_pool_map test_dangling_rank_entry
Test-nvme: auto_md_on_ssd

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 'Some CR functionality tests do not work under md-on-ssd mode'
Status is 'Open'
https://daosio.atlassian.net/browse/DAOS-15589

[saurabhtandan]

Please refer to build# 1 for test results.

[daltonbohning]

This is using md on ssd
https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14312/1/artifact/Functional%20Hardware%20Medium/recovery/pool_list_consolidation.py/daos_configs.wolf-143/daos_server.yml/*view*/

  storage:
  - class: dcpm
    scm_list:
    - /dev/pmem0
    scm_mount: /mnt/daos0
  - bdev_list:
    - '0000:13:00.0'
    - 0000:b0:00.0
    class: nvme

This should use

Skip-func-hw-test-medium-md-on-ssd: false