pg16-timescaledb @2.16.1 conflicts with timescaledb @2.16.0

[barracuda156]

Error: Failed to activate pg16-timescaledb: Image error: /opt/local/lib/postgresql16/timescaledb.dylib is being used by the active timescaledb port.  Please deactivate this port first, or use 'port -f activate pg16-timescaledb' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 49)
    invoked from within
"foreach file $imagefiles {
                incr progress_step
                _progress update $progress_step $progress_total_steps
                se..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                incr progress_step
                _progress update $progress_step $progress_..."

[ryandesign (Ryan Carsten Schmidt)]

Because the files that are now provided by the pg*-timescaledb subports used to be provided by the timescaledb port (if you had installed it with the corresponding +postgresql* variant), the pg*-timescaledb subports need to use the deactivate hack to deactivate timescaledb.

[ryandesign (Ryan Carsten Schmidt)]

Also, it's wrong that timescaledb declares depends_lib pg16-timescaledb; instead, timescaledb should be marked replaced_by pg16-timescaledb and it should use the obsolete-1.0 portgroup. Making this change requires increasing the revision of timescaledb.

[holymonson (Monson Shao)]

In 366526721027f158ed9cc0c33569d685a0962461/macports-ports (master):

timescaledb: fix conflict with subport

• fix conflict with subport
• fix license
• add deactivate hack for smooth upgrade from legacy

Closes: #71189