Update .NET interactive references
This release adopts strong assembly naming. This might cause backwards incompatibility and therefore results in an early major version increase. For more insights why we do this, check out the conversation on this issue