Add sub-RFC for increased availability of NUMA API

[aleksei-fedotov]

Description

Add sub-RFC to #1535 for increased availability of NUMA API.

Type of change

Choose one or multiple, leave empty if none of the other choices apply

Add a respective label(s) to PR if you have permissions

• bug fix - change that fixes an issue
• new feature - change that adds functionality
• tests - change in tests
• infrastructure - change in infrastructure and CI
• documentation - documentation update

Tests

• added - required for new features and some bug fixes
• not needed

Documentation

• updated in # - add PR number
• needs to be updated
• not needed

Breaks backward compatibility

• Yes
• No
• Unknown

Notify the following users

List users with @ to send notifications

Other information

[vossmjp]

Some small wording issues.

[akukanov]

I support this proposal.

[ilya-lavrenov]

but in fact most of Linux OSes has obsolete hwloc versions and relying on it does not provide benefits.
IMO, having most up-to-date static HWLOC together with recent versions of oneTBB has benefits and fixes / new features are available to oneTBB immediately

[aleksei-fedotov]

Thanks, I did not know that. I will consider this in the future changes.

[aepanchi]

I'd rewrite it to smth like this:
1. Reliability. Using a tested and debugged shared library, oneTBB benefits from established, reliable functionality.
2. Code Reuse. Reuse the same code across different processes, improving cache locality and reducing memory footprint, which is the primary purpose of shared libraries.
3. Drop-In Replacement. Use your version of HWLOC without recompiling oneTBB. It can be useful in the following cases:

• You need to apply a hotfix to support your hardware that has not yet been integrated into the HWLOC project.
• You use a HWLOC version that may never be upstreamed. For example, if hardware unavailable to the broader market.
• You want to test a development version of HWLOC on your system.

[aleksei-fedotov]

No necessarily.