`peers` data missing timestamps when restored from cache with --cooldown

[onemen]

Description

The recent enhancements to --format time (introduced in PR #1693) implemented consistent caching and human-readable timestamps. However, the peers data type was omitted during the update. Currently, when peer dependency information is restored from the cache, it lacks the associated timestamp, leading to inconsistent output compared to standard dependencies.

Steps to Reproduce

1. Run ncu --cache --cooldown 5 --peer --format time on a project with peer dependencies to prime the cache.
2. Run the command again to trigger a cache restore.
3. Observe that while standard dependencies display human-readable timestamps, the peer dependencies do not.

Expected Behavior

Peer dependency data should include a time metadata field when cached and restored, matching the implementation for regular dependencies and devDependencies.

@raineorshine

When we are using cooldown we skip cache for cacher.get but not for cacher.getPeers

[onemen]

I will handle it in #1711

in npm.ts

        cooldownInfo: {
          name: packageName,
          currentVersion,
          currentVersionTime: packument?.time?.[current],
          version: tagPackument.version,
          ...maybeTime,
        },

in runLocal.ts and runGlobal.ts

  const time = keyValueBy(latestResults, (key, result) => {
    const time = result.time ?? result.cooldownInfo?.currentVersionTime
    return time ? { [key]: time } : null
  })