doc: update outdated nodejs.org guide links

[HoonDongKang]

Update outdated nodejs.org/en/docs/guides/... links to their current nodejs.org/learn/... destinations.

1. doc/api/cli.md

- https://nodejs.org/en/docs/guides/debugging-getting-started/#security-implications
+ https://nodejs.org/learn/getting-started/debugging#security-implications

2. doc/api/n-api.md

- https://nodejs.org/en/docs/guides/abi-stability/
+ https://nodejs.org/learn/modules/abi-stability

3. doc/api/timers.md

- https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/#setimmediate-vs-settimeout
+ https://nodejs.org/learn/asynchronous-work/event-loop-timers-and-nexttick#setimmediate-vs-settimeout

[nodejs-github-bot]

Review requested:

• @nodejs/node-api

[MikeMcC399]

LGTM!

Thanks for catching the 404 errors!

There are however some other bad links on:

doc/api/cli.md
#environment-variables_1 (underscore instead of -)
https://www.memorymanagement.org/ expired certificate

doc/api/n-api.md
https://gyp.gsrc.io - site no longer exists

Since these issues don't concern nodejs.org, I'd suggest handling them in separate PRs.

I used markdown-link-check directly on the *.md files to check.

[HoonDongKang]

Thanks for pointing these out!

I also ran markdown-link-check and confirmed the failures.

I initially considered addressing all link-check failures under doc/api in a single PR. However, that would have involved changes to many files and made the scope of the PR too broad.

Therefore, I split the fixes into two focused follow-up PRs by file, as suggested:

• doc/api/cli.md: doc: fix broken links in cli.md #65412
• doc/api/n-api.md: doc: fix broken GYP link in n-api.md #65413