Our code occasionally mentions max_bucket_width. However, in practice, there is
no such thing. For fixed-sized buckets, bucket_width and max_bucket_width are
always the same, while for variable-sized buckets bucket_width is not used at
all (except the fact that it equals -1 to indicate that the bucket size is
variable).
This patch removes any use of max_bucket_width, except for arguments of:
- _timescaledb_internal.invalidation_process_hypertable_log()
- _timescaledb_internal.invalidation_process_cagg_log()
The signatures of these functions were not changed for backward compatibility
between access and data nodes, which can run different versions of TimescaleDB.
91f3edf609