Fix incorrect selection of stale-nodes

Currently, the stale-nodes computation will mark a node as stale if any relevant producer_timestamp is older than the node-ttl, when it ought to be checking whether the most recent timestamp is older.

In theory, this could cause nodes to be expired prematurely, though we currently believe that as a practical matter, it's unlikely to happen in current deployments.