Switch buffers over to use the IBufferWriter<byte> and IBufferReader<byte> APIs

[chandler14362]

This opens a lot of new possibilities for what can be accepted by the serialize/deserialize APIs. These APIs are necessary for working with very large data. The serialize state API will be changed to accept a ReadOnlySequence<byte> from ReadOnlySpan<byte>. It's underlying implementation will take advantage of the high-performance System.IO.Pipelines Pipe API, the pipe will be cleaned up once the method accepting the state and ReadOnlySequence<byte> is called. There will also be a serialize API accepting the object and an IBufferWriter<byte>. This API will return void and assume the memory management be handled by the code calling the method. These changes will remove the ability to serialize directly to the stack (unless another solution is made for that specifically). Serialization code will need to be changed to a multi-writer design to pull off the versioning properly, the bookmarks will no longer be usable.