[QUIC] Introduce properties to distiguish uni/bi directional streams

[ManickaP]

ATM moment we're using CanRead|CanWrite to determine whether the stream is uni or bi directional.
Might be useful to introduce Is(Uni|Bi)Directional to distinguish the type of the stream instead of that.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

ATM moment we're using CanRead|CanWrite to determine whether the stream is uni or bi directional.
Might be useful to introduce Is(Uni|Bi)Directional to distinguish the type of the stream instead of that.

Author:	ManickaP
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	Future

[karelz]

Triage: Part of QuicStream API

[ManickaP]

The current implementation of CanRead|Write returns false when the stream is disposed. Whether querying the properties after Dispose is a good or bad idea is a different question. Also we already have the enum for stream creation via connection, so we can take advantage of it.

[wfurt]

There may be other reasons why CanWrite may be false because it depends on internal and peer's state.
That is different IMHO from knowing is the stream was Bidirectional or Unidirectional e.g. even Bidirectional stream can be in state when CanWrite is false.