Fix native addon CI failure by upgrading gyp C++ standard to C++17

[Copilot]

CI job 95299240334 failed because node-addon-api headers now require C++17 features, while the addon target was compiled as C++11. This change aligns addon compile flags with the required standard for Linux and macOS builds.

• Root cause

  • binding.gyp set -std=c++11 for Linux/macOS cflags and cflags_cc, which is incompatible with current node-addon-api usage (std::string_view, std::void_t).

• Change made

  • Updated addon compile standard in binding.gyp:
    • Linux: cflags, cflags_cc → -std=c++17
    • macOS: cflags, cflags_cc → -std=c++17

• Scope guard

  • No workflow/toolchain version changes.
  • No unrelated source or behavior changes.

- "cflags": ["-std=c++11", ...],
- "cflags_cc": ["-std=c++11", ...],
+ "cflags": ["-std=c++17", ...],
+ "cflags_cc": ["-std=c++17", ...],