This is for tracking purposes connected to #1261
I would like to merge TdsParser to a single code base netfx/netcore

The approach I'd like to take is this:

• Do small PR's first which only change code style to align netfx/netcore codebases
• Do small PR's that target specific things (e.g. change from Types to type aliases e.g. Int32 to int)
• Do more PR's that align code but do need code changes

This way (I hope?) changes are small-ish and/or low-riskish, so that they can be reviewed fairly fast (much easier than "big bang" PR's IMHO)

Hope that makes sense, if not just tell me please :)

• Align Newlines: Align newlines between netfx and netcore #2954
• Align whole comments: Align whole comments between netfx and netcore #2955
• Align type aliases Merge | Align Type aliases between netfx and netcore #2957
• Align keywords Align keyword ordering and operation ordering netfx/netcore #2958
• Align var vs Type This one aligns var vs Type between netfx and netcore #2959
• Align redundant namespaces Remove redundant Namespace to align netfx/netcore #2960
• ADP.IsEmpty -> string.IsNullOrEmpty Align ADP.IsEmpty -> string.IsNullOrEmpty #2961
• Align BitConverer -> BinaryPrimitives Merge | Align BitConverter/BinaryPrimitives usage netfx/netcore #2963
• Merge | Align Task usage / ArrayPool / IsColumnEncryptionSupported netcore/netfx #2982
• Merge | Move ReliabilitySection / BestEffortCleanup to framework specific files #2984
• Merge | Align TdsExecuteRPC between netcore and netfx #2985

#2839 also has an impact on this, because removal of SQL 7.0/2000 code means a lot less #IF NETFRAMEWORK constructs, so holding off with aliging SQL7.0/2000 specific code until we know if it needs to stay or can be removed

#3042 Also removes some code that is no longer necessary to merge then