Target .NET Framework 4.6.2 instead of 4.5.2

[frederikprijck]

Changes

With the lowest .NET framework currently supported being 4.6.2, it makes sense to remove our 4.5.2 support and only ship .NET Standard 2.0, which supports 4.6.1 and above.

However, as mentioned here, I makes sense to keep an explicit target for .NET 4.6.2 to improve compatibility.

CONSIDER adding a target for net462 when you're offering a netstandard2.0 target.

Using .NET Standard 2.0 from .NET Framework has some issues that were addressed in .NET Framework 4.7.2. 
You can improve the experience for developers that are still on .NET Framework 4.6.2 - 4.7.1 by offering them a binary that's built for .NET Framework 4.6.2.

References

https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-framework

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors

[Hawxy]

Heads up that the recommendation is to keep at least a net462 target if using .NET Standard 2.0. Although 4.6.2 "supports" .NET Standard 2.0, it can randomly break and cause dependency resolution issues. See https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting

CONSIDER adding a target for net462 when you're offering a netstandard2.0 target.

Using .NET Standard 2.0 from .NET Framework has some issues that were addressed in .NET Framework 4.7.2. 
You can improve the experience for developers that are still on .NET Framework 4.6.2 - 4.7.1 by offering them a binary that's built for .NET Framework 4.6.2.

[frederikprijck]

That's actually good to know, will revert the last commit.

Thanks @Hawxy