perf: Increasing Network Writer performance (MirrorNetworking#1674)

* Increasing performance of network writer

* Using Array.Clear

renaming value to newLength

* Update Assets/Mirror/Tests/Editor/NetworkWriterTest.cs

Co-Authored-By: Paul Pacheco <[email protected]>

* adding braces

* extracting EnsureCapacity method

* Update NetworkWriter.cs

Co-authored-by: Paul Pacheco <[email protected]>
Co-authored-by: vis2k <[email protected]>

perf: Use continuewith to queue up ssl messages (MirrorNetworking#1640)

get rid of the complicated queue. Use Task.continuewith 

also,  apparently we have to flush or latency is really bad.

adding Category to weaver and Telepathy tests (MirrorNetworking#1643)

Fixed comment in template

perf: faster NetworkReader pooling (MirrorNetworking#1623)

* replacing stack with array for NetworkReaderPool

* Reader tests

perf: faster NetworkWriter pooling (MirrorNetworking#1620)

* using array in NetworkWriterPool instead of stack

* Using property

adding debug warning if pool is full

* adding tests for  NetworkWriterPool

* Update NetworkWriterPool.cs

* Update NetworkWriterPoolTest.cs

Co-authored-by: vis2k <[email protected]>

Revert "perf: faster NetworkWriter pooling (MirrorNetworking#1616)"

This reverts commit 5128b12.

perf: faster NetworkWriter pooling (MirrorNetworking#1616)

Stack turned out to be slow way to pool NetworkWriters.
Replace them with an array

see MirrorNetworking#1614

perf: replace isValueType with faster alternative (MirrorNetworking#1617

)

According to vis benchmark here MirrorNetworking#1614 (comment)
isValueType is an expensive operation.

This microoptimization replaces isValueType for a faster (not so readable) alternative

perf: use byte[] directly instead of MemoryStream (MirrorNetworking#1618

)

* perf: use byte[] directly instead of MemoryStream

* Optimize writing int32 and int64

* Update Assets/Mirror/Runtime/NetworkWriter.cs

Co-Authored-By: vis2k <[email protected]>

* Update Assets/Mirror/Runtime/NetworkWriter.cs

Co-Authored-By: vis2k <[email protected]>

* Update Assets/Mirror/Runtime/NetworkWriter.cs

* Start with bigger buffer

* Woops,  should have double checked suggestion

* Removed invalid Test

We should not require NetworkWriter to behave in certain way when Position
is set to out of bounds.

That is an invalid use of NetworkWriter, so NW should be free to do any behavior

* smells

* Update NetworkWriter.cs

Co-authored-by: vis2k <[email protected]>