Update fast truncate to use newest start durable ts

At present fast truncate checks, the possibility of deleting entire page based on the oldest start timestamp of the aggregated time window information. This is wrong, as oldest start timestamp represents the earliest update of the page, whereas truncate should depend on the visibility of the newest update (i.e. if the newest update is visible to truncate then only delete can be performed at page level).