Update `MAX_PATH` guidance for `LongPathsEnabled`?

[karlhorky]

The MAX_PATH explanation and workarounds guide by @mousetraps seems like a nice set of workarounds and explanation, but seems outdated now (eg. mentions npm v3, doesn't mention LongPathsEnabled)

If LongPathsEnabled is enabled on Windows, is there guidance for getting long paths supported in Node.js as well? Or is there a bug tracking this 260+ characters long paths support in Node.js?

Context:

1. I am not sure if I'm understanding the details of internal Node.js support of long paths yet, but I do see this comment by @bzoz that "Node uses file namespace paths for file access. We do that so we do not get hit by the 260 path limit," - maybe this only applies to writeFile?
2. The reason I started all of this is that I'm currently coming from this ESLint bug, which occurs when ESLint tries to import long node_modules paths Bug: Long node_modules plugin paths cannot be found on Windows eslint/eslint#17763

It would be great to get support for long file paths on Windows in Node.js!

[karlhorky]

I also opened an issue in Node.js to see whether the 260 character limit is expected:

• Long node_modules paths cannot be found on Windows when LongPathsEnabled enabled nodejs/node#50753

[karlhorky]

Node.js 22.7.0 no longer has long paths problems on Windows, when LongPathsEnabled is set:

• Long node_modules paths cannot be found on Windows when LongPathsEnabled enabled nodejs/node#50753 (comment)