fix(core): Disable Fast Fallback for network connections (no-changelog)

[netroy]

Summary

Node.js 20 enabled Happy Eyeballs algorithm for all dual-stack network calls by default.
This has turned out to be an issue with certain services like Telegram and Airtable, that are not responding to their IPv6 addresses in a timely manner.
There have been a couple of fixes to Node's implementation of this algorithm, but there seem to be still some bugs present for our users.
Until one of us understand this issue a bit more, and can track the issues on Node.js, I suggest that we disable socket autoSelectFamily by default, like it used to be on Node.js 18.

Related Linear tickets, Github issues, and Community forum posts

https://community.n8n.io/t/errors-since-last-n8n-update-1-44-1/48238
#9824

Review / Merge checklist

• PR title and summary are descriptive

[tomi]

🚀

[cypress]

5 flaky tests on run #5675 ↗︎

0

395

0

0

5

Details:

🌳 🖥️ browsers:node18.12.0-chrome107 🤖 netroy 🗃️ e2e/*
Project: n8n	Commit: 10008c311f
Status: Passed	Duration: 05:21 💡
Started: Jun 26, 2024 8:29 AM	Ended: Jun 26, 2024 8:34 AM

  5-ndv.cy.ts • 3 flaky tests

View Output Video

Test		Artifacts
NDV > should not retrieve remote options when required params throw errors		Screenshots Video
NDV > should retrieve remote options when non-required params throw errors		Screenshots Video
NDV > Stop listening for trigger event from NDV		Screenshots Video

  10-undo-redo.cy.ts • 2 flaky tests

View Output Video

Test		Artifacts
Undo/Redo > should undo/redo adding nodes		Test Replay Screenshots Video
Undo/Redo > should undo/redo adding connected nodes		Test Replay Screenshots Video

Review all test suite changes for PR #9860 ↗︎

[github-actions]

✅ All Cypress E2E specs passed

[github-actions]

✅ All Cypress E2E specs passed

[janober]

Got released with n8n@1.47.1

[dkindlund]

Hey @janober , does Deborah (https://community.n8n.io/u/deborah/summary) have a GitHub user account to ping?

The reason I ask, is because she had a community post not long ago asking for how the n8n documentation can be improved.

I would argue this PR is Exhibit A of what absolutely needs to be included in the Release Notes here:
https://docs.n8n.io/release-notes/#n8n1471

For those n8n community users who want to upgrade regularly:

• they will likely upgrade to n8n@1.46.0 (which is currently marked as "latest" at the time of this post)
• then, they'll get bitten by this bug in the PR
• hunt through the forums, issue tracker, and PR to figure out why things broke
• and then re-upgrade to n8n@1.47.1 (pre-release) (again)

To minimize this recurring pain for users, could these sorts of breaking issues be called out directly either in the 1.47.1 release notes OR in the earlier 1.46.0 release notes -- something like a warning of:

WARNING: If you are upgrading to 1.46.0, we strongly recommend you upgrade to 1.47.1 because of this issue... etc...

Again, having some sort of PR tag to likerelease/update-note-needed (or something like that) may be a good mechanism to notify Deborah about these sorts of issues in a consistent manner.

Thanks for your time.