Explicit logging of cache key and restore key matches

[Link-]

Fixes: actions/cache#1626

Improve logging for cache restoration in the restoreCacheV2 functionality. It adds more specific log messages to differentiate between cache hits for exact keys and restore keys, enhancing debugging and traceability.

[Copilot]

Pull Request Overview

This PR improves cache restoration logging in the restoreCacheV2 functionality by adding explicit differentiation between exact cache key matches and restore key matches. This enhancement addresses issue #1626 by providing clearer debugging information during cache operations.

• Replaces generic cache hit logging with specific messages for exact vs restore key matches
• Adds logic to determine if the matched key differs from the requested key
• Updates test cases to verify the new logging behavior

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/cache/src/cache.ts	Implements conditional logging logic to distinguish between exact key and restore key cache hits
packages/cache/tests/restoreCacheV2.test.ts	Adds test assertions to verify the new logging messages are generated correctly

Comments suppressed due to low confidence (1)

packages/cache/src/cache.ts:267

• The variable name 'isRestoreKeyMatch' is misleading. When request.key !== response.matchedKey, it indicates a restore key was matched, but the variable name suggests it's checking if it IS a restore key match. Consider renaming to 'isExactKeyMatch' with inverted logic or 'matchedRestoreKey' for clarity.

    const isRestoreKeyMatch = request.key !== response.matchedKey

[GhadimiR]

LGTM