Fix #2804: Use chroma-js for all color parsing and conversion

[f3rnando0]

Summary

Refactered color parsing and conversion functions to use chroma-js methods as described in the issue #2804.

General checklist

• Methods changed
  • hexToHsv
  • hexToRgb
  • hsvToHex
  • hsvToRgb
  • rgbToHex
  • isValidHex - Didn't change this function because chroma-js.valid method allows hex strings that don't start with #, which implies with the tests, so I just added a comment about it and remained the regex test.

[cla-checker-service]

💚 CLA has been signed

[github-actions]

👋 Since this is a community submitted pull request, a Buildkite build has not been started automatically. Would an Elastic organization member please verify the contents of this pull request and kick off a build manually?

[github-actions]

👋 Since this is a community submitted pull request, a Buildkite build has not been started automatically. Would an Elastic organization member please verify the contents of this pull request and kick off a build manually?

[tkajtoch]

Thanks for your contribution, @f3rnando0! Before we review it, we need to consider potential performance implications this may cause. Chroma.js is pretty slow when converting certain color formats, resulting in highly increased emotion style function evaluations.

I've experienced ~3ms conversion times running on M2 Pro that I consider the top end of our users' CPUs. Since the styles need to be computed before the initial component render, this delay blocks components from being rendered "immediately" (let's forget about the react scheduler for the sake of this conversation), and due to the synchronous nature of how Emotion styles are being loaded, child components' functions can only be executed once Chroma finishes its calculations risking creating a cascading effect when used in multiple nested components.