timescaledb vs redis

[feierabend654]

This changeset adds timescaledb integration for storing and loading candles.

There are some dev scripts for one to try it out locally - ./run-dev-timescale.sh; ./run-dev-timescale-migrations.s will start timescale with an external data volume and also run the necessary setup migrations. Currently I have setup a compression bucket interval of a day and also uses the symbol column. Would appreciate some input on common access patterns to refine this.

There is another script yarn timescale-perf-test-bulk-load to bulk load one month old random data for stress testing.

And finally there are some logs sprinkled which do basic timing of storing and fetching from redis and timescale.

Also, maybe, we want to do some error handling around timescale interaction, or fail hard, not decided, lets discuss

[feierabend654]

Extended the redis script to mount a dump, see run-dev-redis.sh

Also, added a simple migration (redis->timescale) script, can be run so ./run-dev-timescale.sh; ./run-dev-timescale-migrations.sh; yarn timescale-migrate-from-redis;, this basically resets timescale instance, and migrates redis data to timescale

[BunnyNomics101]

@feierabend654 We have been trying to run this for our dex as web socket API. It deployed successfully on port 8900 but there is no signal.