Reduce dependency on CultureInfo.Current and Thread Current culture.

[adamhathcock]

Thanks for this, I'm using this now on a .NET Core 3 project and seems like it's working!

I was attempting to use Money.TryParse which always uses Currency.CurrentCurrency which always throws because (I believe) .NET Core's current culture is always invariant.

Using the overload of TryParse that specifies a currency works but I'd rather the parse try to figure it out (sometimes).

Anyway, I went down a rabbit hole trying to have it not throw for CurrentCurrency but that seems to break a lot as well as the unit tests fail as it relies a lot on CurrentCulture and/or CurrentCurrency.

Does 2.0 have plans to (nearly) remove this default? .NET 5 is almost here and I'd like to help remove some legacy stuff like current culture and reliance on legacy frameworks.

Let me know your plan and I can find some time to help out!