Drop access to TCP tuning options outside of the stream scope

[pfreixes]

What do these changes do?

Before this commit, the TCP tunning was allowed from PayloadWriter
and Response classes, this was exclusively used by just some edge cases and
caused some overhead in performance and maintainability.

Since now, the TCP tunning has to be done using the stream and its
the responsibility of the developer set and set back the proper values.

Are there changes in behavior for the user?

No

Related issue number

#2604

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> for example (588.bug)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

[codecov-io]

Codecov Report

Merging #2612 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #2612      +/-   ##
=========================================
+ Coverage   97.88%   97.9%   +0.01%     
=========================================
  Files          38      38              
  Lines        7344    7314      -30     
  Branches     1270    1270              
=========================================
- Hits         7189    7161      -28     
+ Misses         51      49       -2     
  Partials      104     104

Impacted Files	Coverage Δ
aiohttp/web_response.py	98.18% <ø> (-0.08%)	⬇️
aiohttp/http_writer.py	99.42% <ø> (+1.07%)	⬆️
aiohttp/web_protocol.py	89.42% <100%> (-0.11%)	⬇️
aiohttp/web_fileresponse.py	97.88% <100%> (-0.05%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c178a99...a84cb75. Read the comment docs.

[fafhrd91]

Lgtm

This change is fine. Though, other developers should check this. As I remember @socketpair originally proposed support for nodelay and cork

[asvetlov]

@pfreixes please merge

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new