Remove several dependencies

[patrikwlund]

This library has a lot of dependencies for a library, several of which seem unnecessary.

Description

All applications depending on this library will transitively inherit all of its dependencies. The more libraries, the bigger the risk of conflicts, and also the bigger the potential attack surface (e.g. take-overs or sneaky PRs).

We use Vonage for its services, but we don't want to inherit random dependencies if we can avoid it. Especially small "unknown" ones.

I removed/replaced three libraries:

• Epoch.net - easily replaced by DateTimeOffset.UtcNow.ToUnixTimeSeconds()
• Yoh.Text.Json.NamingPolicies - does not seem to be in use
• Handy.DotNETCore-Compatibility.ColorTranslations - i inlined the code

How Has This Been Tested?

The test suite passes in both NET 6 and NET 8.

[Tr00d]

Hi @patrikwlund,

Thanks for contributing. You'll find my thoughts below:

• Epoch.net
  Indeed, that one can easily be replaced.

• Yoh.Text.Json.NamingPolicies
  Indeed, that dependency stopped being used by end of 2023. Based on what I see, System.Text.Json introduced new JSON naming policies - specifically the one required (snake case). It's clearly a remnant that should be removed.

• Handy.DotNETCore-Compatibility.ColorTranslations
  While I agree with the reason behind, I disagree with your proposal. You're basically putting the code from 'https://github.com/stephenhand/.NETCore-Compatibility-Helpers/blob/master/src/ColorTranslations/ARGB.cs' inside the codebase, with hardcoded colour codes which now become my responsiblity to maintain. I'm okay to get rid of that dependency, but not this way.
  Now, the ColorConverter is used in a single API... which is deprecated/obsolete and will be removed in the next major version. What I can do is try to get to that version faster and simply get rid of the dependency. The version didn't change since I started using the lib (0.2.1) but I can force that version to make sure there's no update until then.

[patrikwlund]

Hi @patrikwlund,
While I agree with the reason behind, I disagree with your proposal. You're basically putting the code from 'https://github.com/stephenhand/.NETCore-Compatibility-Helpers/blob/master/src/ColorTranslations/ARGB.cs' inside the codebase, with hardcoded colour codes which now become my responsiblity to maintain. I'm okay to get rid of that dependency, but not this way.
Now, the ColorConverter is used in a single API... which is deprecated/obsolete and will be removed in the next major version. What I can do is try to get to that version faster and simply get rid of the dependency. The version didn't change since I started using the lib (0.2.1) but I can force that version to make sure there's no update until then.

I think you're worried for no reason since it hasn't had a need to change at all in the last 9 years, and it would just be internal code, but I think your suggestion is reasonable.

I reverted the relevant commit. Do you usually squash-merge, or would you like me to squash the commits beforehand?

[Tr00d]

It's a matter of months before the next major release, but I'll try to shrink that.
In the meantime, I'll create an issue on the repo to make sure it stays visible.

No worries, I'll squash it myself