Fix DeviceDetectorCache cache eviction flakiness

[tzi]

Description

This PR fixes flaky cache eviction behavior in the DeviceDetectorCache plugin.

When cached device detector entries are reused, their access time is now refreshed before eviction decisions are made. This makes cache cleanup behave like an LRU-style policy and prevents recently used cache files from being deleted unexpectedly.

Changes

• Refresh cache file access time when a cached entry is loaded.
• Keep deleteLeastAccessedFiles() based on access time, but make the recorded access time meaningful by updating it on reads.
• Update the integration test to reflect the correct entry that should remain after the second warm-cache run.

Why

WarmDeviceDetectorCacheTest::testDoesClearExistingFilesFromCacheByDefaultWhenTooManyEntriesExist was flaky because reading a cached entry did not update its file access time. As a result, cleanup could delete an entry that had just been reused.

Testing

• Updated WarmDeviceDetectorCacheTest to assert the recently accessed cache entry is preserved.
• The new behavior matches the intended “delete least accessed files” logic.

Checklist

• [✔] Tested locally or on demo2/demo3?
• [✔] New test case added/updated?
• [✔] Are all newly added texts included via translation?
• [✔] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
• [✔] Version bumped?
• [✔] I have understood, reviewed, and tested all AI outputs before use
• [✔] All AI instructions respect security, IP, and privacy rules