Allow loading dependencies by name

[aleksei-fedotov]

Description

This PR allows loading dependencies by module name only as it is proposed in this RFC. To strengthen the security and avoid loading malicious code, the signature verification for modules being loaded is also introduced.
However, to avoid breaking compatibility with existing scenarios, the signature verification is disabled by default. To notify about that the following CMake warning appears on the console when cmake command is invoked for the first time:

CMake Warning at CMakeLists.txt:142 (message):
  Dependency signature verification during dynamic linking in run-time is
  disabled by default.  This may lead to security vulnerabilities.  See
  installation section in oneTBB documentation for more details.

, drawing user's attention to this change and allowing to explicitly choose whether user wants unsigned or having incorrect signature modules to be loaded or not.
To avoid loading of such modules, user needs specifying -DTBB_VERIFY_DEPENDENCY_SIGNATURE=ON flag in the invocation command of CMake. In this case the warning transforms in a regular status message of the form:

-- Dependency signature verification during dynamic linking in run-time is ENABLED

If, however, user ignores the warning, the following invocations of cmake command show that the signature verification setting remains disabled:

-- Dependency signature verification during dynamic linking in run-time is DISABLED

The patch also adds optional reporting of dynamic link issues. Examples of the output:

oneTBB dynamic link warning: The module "<path-to-dll>" is unsigned or has invalid signature.
oneTBB dynamic link warning: The module "<path-to-dll>" was not found. System error: 126

The issues reporting is disabled by default and can be enabled by setting TBB_DYNAMIC_LINK_WARNING macro during the build.

[egfefey]

From the security standpoint, this is good for now.
A few notes:

• This is still up for discussion but anything beside ERROR_SUCCESS from WinVerifyTrust should result in an error instead of a warning sometimes. The user always has to option to turn off signature verification if they want, so once it's on, it's either success or failure.
• Might also need review from the TBB team.
• If there are some testing results that we can share, that will be great.

[egfefey]

Update to use SearchPathA is good from the security point of view.

[aleksei-fedotov]

Update to use SearchPathA is good from the security point of view.

Thanks, @egfefey! Then I proceed with productization of this patch.

[kboyarinov]

LGTM overall but I didn't review warnings and error codes in details

[omalyshe]

@aleksei-fedotov Please adjust the description because signature check is now OFF by default.