Remove setNoDelay call to response socket

[Supereg]

♻️ Current situation

Currently, we set the setNoDelay tcp option for our internal http/tcp server, running for every connection.
This seemingly causes issues as identified in homebridge/homebridge#3226 (comment).
Particularly, according to the documentation, the property response.connection might be nulled once response.end() was called on it.

💡 Proposed solution

This PR removes this call, as request.socket and response.connection are the same object anyways.

⚙️ Release Notes

• Fixed a potential crash occurring in some rare situations when handling http requests.

➕ Additional Information

• Reported in Rebooting system homebridge#3226

Testing

--

Reviewer Nudging

--

[coveralls]

Pull Request Test Coverage Report for Build 3072448646

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.07%) to 51.683%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/lib/util/eventedhttp.ts	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/lib/util/eventedhttp.ts	1	21.66%

Totals
Change from base Build 3043933152:	-0.07%
Covered Lines:	5715
Relevant Lines:	10090

---

💛 - Coveralls