fix!: resolve issue with relative paths during linking

[Dw9]

nodejs/node-gyp#3128

[legendecas]

LGTM.

Searching through usages on library_dirs: https://github.com/search?type=code&q=library_dirs+path%253A*.gyp. It seems to me there are relative paths in library_dirs in the wild that will be break by this change. I think this PR should be released as a breaking change.

[legendecas]

Would you mind updating the list in the document https://github.com/nodejs/gyp-next/blob/main/docs/InputFormatReference.md#pathname-relativization as well?

library_dirs is suffixed with _dirs, should be treated as pathnames and be included in pathname relativization. As it is built-in config key, I believe it is better to explicitly list it here.

Thank you!

[legendecas]

• cmake:

  gyp-next/pylib/gyp/generator/cmake.py

  Line 817 in 46fc91f

  output.write(NormjoinPath(path_from_cmakelists_to_gyp, library_dir))

• ninja:

  gyp-next/pylib/gyp/generator/ninja.py

  Line 1491 in 46fc91f

  QuoteShellArgument("-L" + self.GypPathToNinja(library_dir), self.flavor)

• msvc:

  gyp-next/pylib/gyp/generator/msvs.py

  Line 3354 in 46fc91f

  library_dirs = _GetLibraryDirs(configuration)

Seems like we don't have tests on this, but it will be great if you can update these generators as well to keep them in align.

[Dw9]

hi～@legendecas； I'm not very familiar with the project and don't know how to test with cmake/nanja/msvc. Could you please advise on how to make modifications?