[Question] Refactor to use `vx` as backend in place of d3

# 🌈Feature request

Looking thru the component sources, I've noticed that they are built some d3 placed in `componentDidMount` (especially axes) which makes react development difficult because it's bypassing the react rendering engine.

I just came across a library called [vx](https://vx-demo.now.sh/) which describes itself as a low level charting interface for d3 using React/jsx. I wonder what you would think about moving towards implementing `react-timeseries-charts` on top of `vx`?

I realize this isn't a trivial change so no pressure to make any large movements towards it, but it seems like it could help reduce the complexity of the backend for this package for the next big version.

Start by reviewing the component sources, especially the chart logic currently placed in componentDidMount, and compare that approach with the vx interface described in the issue. Determine the scope of replacing the d3-backed implementation with vx across the package; done would require an agreed migration plan or implementation covering the affected components.

Written by the indexing model from the issue text.