Resharding always write new collection timestamp

In SERVER-58589 we removed the ShardingFullDDLSupportTimestampedVersion flag so that we always use timestamps in collection metadata.

We forgot to cleanup some resharding code that still support the old metadata format. In particular the writeDecisionPersistedState still accepts a boost:optional<Timestamp> when there must not be a case in which we don't have an actual timestamp.