This update for timescaledb fixes the following issues:

- postgresql18 enablement.

- Update to version 2.24.0

  This release contains performance improvements and bug fixes
  since the 2.23.1 release. We recommend that you upgrade at the
  next available opportunity.

  Highlighted features in TimescaleDB v2.24.0

  - Direct Compress just got smarter and faster: it now works
    seamlessly with hypertables generating continuous aggregates.
    Invalidation ranges are computed directly in-memory based on
    the ingested batches and written efficiently at transaction
    commit. This change reduces the IO footprint drastically by
    removing the write amplification of the invalidation logs.
  - Continuous aggregates now speak UUIDv7: hypertables partitioned
    by UUIDv7 are fully supported through an enhanced time_bucket
    that accepts UUIDv7 values and returns precise, timezone-aware
    timestamps — unlocking powerful time-series analytics on modern
    UUID-driven table schemas.
  - Lightning-fast recompression: the new recompress := true option
    on the compress_chunk API enables pure in-memory recompression,
    delivering a 4–5× speed boost over the previous disk-based
    process.

- ARM support for bloom filters
  The sparse bloom filter indexes will stop working after upgrade
  to 2.24. If you are affected by this problem, the warning "bloom
  filter sparse indexes require action to re-enable" will appear in
  the Postgres log during upgrade.

  In versions before 2.24, the hashing scheme of the bloom filter
  sparse indexes used to depend on the build options of the
  TimescaleDB executables. These options are set by the package
  publishers and might differ between different package sources or
  even versions. After upgrading to a version with different