Multi TSDB introduced the ability to run multiple TSDBs in one Thanos receive node allowing on disk multi-tenancy within the same process. During the migration we noticed an odd behavior, being a TSDB that was once started, will never be cleaned up if it's not actively ingesting samples. This is due to how compaction is triggered in TSDB, which only happens on `Commit` calls to the database.

TSDBs whose data has been uploaded, and the WAL is empty, should be closed and not started on boot of the receive node.