Jasper

Closing and reopening PR to re-trigger Travis CI build

@NickCraver Primarily I would like to use `UnflushedBytes` and `ReadAtLeastAsync`, otherwise I would need to do the accounting myself. I believe upgrading SIOP alone shouldn't break anyone, given that even...

>You can always use a newer version in your downstream project as long as there are no breaking changes in that newer version, the library doesn't need to require everyone...

I've reverted all non-necessary changes, added .net6 as a new target. and upgraded SIOP only for .net6 as suggested. I'll file a separate PR with test fixes.

Like @sixlettervariables https://github.com/nats-io/nats.net/pull/447#issuecomment-834477949 I'm using a slightly modified version of the .editorconfig from dotnet/runtime. It uses UPPER_SNAKE_CASE for private const fields which matches about two thirds of the private consts...

@ColinSullivan1 I'm honestly not sure anymore, if this whole endeavour is feasible. Up until yesterday test runs were mostly failing on Mac OS which I was about to ignore. But...

Yeah, I had no hope to get to some reasonable pipeline pass rate. With your fix for TestAsyncInfoProtocolPrune this may be feasible. I'll see if I find a way to...

Sorry, I should have been more clear. Integration tests generally work on Mac but fail way more often than on Linux/Win. OSX runs caused the majority of pipeline failures before...

@ColinSullivan1 I pushed some more changes, reopening to get a up to date delta. Pipeline pass rate is [still way to low](https://dev.azure.com/jasperd/nats.net/_build?definitionId=6), but most of these failures are caused by...

@Sergey-Terekhin Would you mind to try [this patch](https://github.com/nats-io/nats.net/compare/master...jasper-d:fix-ip#diff-8d419c788b0712057106362cdb85792218a222a49f901e5ae624e3624ecabdc0)? I haven't tested it on k8s where we have issues with 0.11.0, but on my machine nats.net works just fine again when...