DAOS-14408 common: ensure NDCTL not used for storage class ram

[grom72]

This PR prepares DAOS to be used with NDCTL enabled in PMDK, which means:

• NDCTL must not be used when non-DCPM (simulate PMem) - storage class: "ram" is used:
  PMEMOBJ_CONF=sds.at_create=0 env variable disables NDCTL features in the PMDK
  This change affects all tests run on simulated PMem (e.g. inside VMs).
  Some DOAS utility applications may also require PMEMOBJ_CONF=sds.at_create=0 to be set.

• The default ULT stack size must be at least 20KiB to avoid stack overuse by PMDK with NDCTL enabled and be aligned with Linux page size.
  ABT_THREAD_STACKSIZE=20480 env variable is used to increase the default ULT stack size.
  This env variable is set by control/server module just before engine is started.
  Much bigger stack is used for pmempool open/create-related tasks e.g. tgt_vos_create_one to avoid stack overusage.

This modification shall not affect md-on-ssd mode as long as storage class: "ram" is used for the first tier in the storage configuration.
This change does not require any configuration changes to existing systems.

The new PMDK package with NDCTL enabled (daos-stack/pmdk#38) will land as soon as this PR is merged.

Based on: #14371

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 'NDCTL must be enabled to provide support for RAS functionality in PMDK'
Status is 'Awaiting backport'
Labels: 'scrubbed_2.8,triaged'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-14408

[daosbuild1]

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-15203/1/testReport/

[grom72]

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-15203/8/ has NLT failures which I don't think are related to the PR
All other tests passed in https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-15203/7/