Fix SNIPacket.ReadFromStreamAsync to not consume same ValueTask twice (dotnet/corefx#42338)
Found via an analyzer I'm working on for ValueTasks.
This calls stream.ReadAsync, and in the case where the ValueTask completes successfully by the time the code checks and where the returned Result <= 0, it then awaits the ValueTask again, representing a second consumption when only one is considered legal.
Fix it by replacing the original ValueTask with a new one containing the same result.
Commit migrated from https://github.com/dotnet/corefx/commit/
a7cebb9ce454be31a0467ed418a221e5e3009768