Control `pathSuffix` option via configuration file(s)

未指定原始碼檔案或測試。首先追蹤 pathSuffix 如何傳遞給 Babel 外掛程式和主機套件 CLI，包括 pod install 或 Gradle 建置期間的 NODE_API_PATH_SUFFIX，同時檢視 pull request 104 可能造成的影響。當應用程式範圍或依程式庫設定能在不需要個別執行階段設定的情況下，一致地控制該選項時，即視為完成。

We're performing a transformation of the Node-API addon dynamic library paths on disk to their dynamic library names as they're linked into the host package.

Here's the documentation for the pathSuffix option of the NamingStrategy:

Controls how the path of the addon inside a package is transformed into a library name.
The transformation is needed to disambiguate and avoid conflicts between addons with the same name (but in different sub-paths or packages).

As an example, if the package name is my-pkg and the path of the addon within the package is build/Release/my-addon.node:

• "omit": Only the package name is used and the library name will be my-pkg.
• "strip": Path gets stripped to its basename and the library name will be my-pkg--my-addon.
• "keep": The full path is kept and the library name will be my-pkg--build-Release-my-addon.

In the current state, this pathSuffix option is passed to the babel plugin as well as to the host package's CLI (either through a CLI runtime option or more likely the NODE_API_PATH_SUFFIX environment variable while running pod install or the Gradle build) and they need to match for the app to find the dynamic library files at runtime.

It would be more flexible and less brittle if ☝ was instead determined by

• a single app-wide configuration setting, either in configuration file (or a key in the App's package.json) and / or
• by individual per-library configuration files (or a key in their package.json files)

[!NOTE]
This will likely all change once https://github.com/callstackincubator/react-native-node-api/pull/104 merge.