streams: update .readable/.writable to false

[mscdex]

These properties were initially used to determine stream status back in node v0.8 and earlier. Since streams2 however, these properties were always true, which can be misleading for example if you are trying to immediately determine whether a Writable stream is still writable or not (to avoid a "write after
end" exception).

This is #1217 targeting the master branch and with a couple of minor changes to fix a lint error and to help address a concern about .on().

[mscdex]

CI is all green.

@chrisdickinson I've replaced the additional conditional used in .on() instead of removing it now. Does this LGTY?

[chrisdickinson]

LGTM!

[mscdex]

Landed in cc0342a.

[jasnell]

@mscdex ... how would you rate the semver'iness of this change? Should this go into v4?

[jasnell]

Marking this as lts-watch for v4 but please do not land in v4.x-staging until confirmed

[mscdex]

@jasnell I would say no for v4 as it's more like a semver-major since it changes property values of existing properties (for readables it sets .readable = false sooner and for writables it actually sets .writable = false now).

[MylesBorins]

adding semver-major tag and removing LTS watch. Please feel free to update if I was incorrect in doing so

edit: if we do add it back to LTS we need to add the tag back to #4141 as well