cooldown seens to ignore versions that are old enough

- [x] I have searched for [similar issues](https://github.com/raineorshine/npm-check-updates/issues) --- ## Steps to Reproduce .ncurc: ```js cooldown: 7 ``` Dependencies: I have tested this problem on my global dependencies, but I also have projects that show the same effect. The current state of my global dependencies is ``` > npm -v 11.12.1 >npm ls -g C:\nvm4w\nodejs -> .\ +-- @angular/cli@21.2.7 +-- @google/gemini-cli@0.37.1 +-- corepack@0.34.7 +-- npm-check-updates@20.0.1 +-- npm@11.12.1 +-- pnpm@10.33.2 `-- yarn@1.22.22 ``` Steps: <!-- The exact steps taken to arrive at the unexpected behavior. --> ## Current Behavior <!-- Describe the existing (incorrect) behavior. --> 1. `ncu -g` 2. result: ``` Using config file C:\Users\Berni\.ncurc [====================] 7/7 100% npm 11.12.1 → 11.13.0 ncu itself cannot upgrade global packages. Run the following to upgrade all global packages: npm -g install npm@11.13.0 ``` No ther package is proposed for update. But npm-check-updates could be updated to v22.0.0 as this version was published 8 days ago (today is 2026-05-03). npmjs shows the following versions / dates <img width="1108" height="540" alt="Image" src="https://github.com/user-attachments/assets/db5bce46-e0b8-4f9b-bff8-ff4650dae6fd" /> ## Expected Behavior <!-- Describe the desired behavior. --> Proposed updates should include `npm-check-updates@22.0.0` (and others packages too)