Log Message:
promscale: update to 0.2.2.0

Adds support for Multinode TimescaleDB.
Improved promQL query latency by 4x in some cases.
Reduced I/O used by the PostgreSQL stats collector substantially by
  changing autovacuum settings.
  Fixed metrics produced by Promscale itself
PromQL engine supports @ modifier which is disabled by default.
  (see promql-evaluation-flags)
Added configuration for query timeout and default step interval
Improved UX

Notes for people upgrading from 0.1.4 and before

The CLI and ENV option install-timescaledb was renamed to install-extension
Two new flags are added upgrade-extensions by default set to true will
upgrade extensions if newer versions are available and
upgrade-prerelease-extensions by default set to false enabling it will
upgrade extensions to pre-prelease versions if pre-release versions are
available.

We have changed the namespace of the metrics Promscale itself exposes from
ts_prom to promscale. We have also updated the PromQL engine based metrics
to have namespace as promscale instead of prometheus. So, metrics like
prometheus_engine_query_duration_seconds will now be
promscale_engine_query_duration_seconds.
If running into ERROR: out of shared memory (SQLSTATE 53200) during upgrade,
please increase your max_locks_per_transaction setting.

Notes for people upgrading timescaleDB 1.x -> 2.x

You should run
SELECT remove_compression_policy(format('prom_data.%I', table_name),
       if_exists=>true) FROM _prom_catalog.metric;
after the upgrade. This cleans up the old way of running compression jobs,
compression will still work (just in the new way).

Prom-Migrator

Adds support for concurrent pulling and pushing to improve migration
throughput. (Please note concurrent push is disabled by default as we've
seem some issues migrating data to Thanos concurrently, which we are still
working out).