Remove binary serialization

[iamcarbon]

Binary serialization support is no longer recommended as .NET5.0 and is obsoleted entirely in .NET 8.0 in preparation for its removal in .NET 9.0.

https://github.com/dotnet/designs/blob/main/accepted/2020/better-obsoletion/binaryformatter-obsoletion.md

This PR removes binary serialization support on Exceptions (and eliminates the warnings when targeting .NET8.0) -- and helps ensure no-one relies on these when support is removed in .NET 9.0.

[iamcarbon]

@abergs Ready for review.

[abergs]

@iamcarbon what side effects would this cause?

[iamcarbon]

Users serializing exceptions using the BinaryFormatter would no longer work. This was common on the .NET Framework where logging libraries would intercept errors and log them somewhere. I don't think this pattern ever carried over to .NET core, and I'm unaware of any modern libraries that still use the BinaryFormatter. New exceptions introduced to modern .NET haven't been annotated for years, and we never annotated all our exceptions in this library either.

If someone happens to be using binary serialization on modern .NET, they should be migrating away ASAP. The BinaryFormatter is obsolete, unsafe, and being prepared for removal in .NET 9.0.

https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter?view=net-8.0

[iamcarbon]

@aseigler Let me know if you see any reason not keep these around. These attributes cause an error on .NET 8.0 and will be need to be suppressed if we want to continue to support them on .NET 6.0.