Set last-access-time for only LRU records

[ahmetmircik]

follow-up of #18624

[hz-devops-test]

The job Hazelcast-pr-builder of your PR failed. (Hazelcast internal details: build log, artifacts).
Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log file

--------------------------
-------TEST FAILURE-------
--------------------------
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   ExpirationTimeTest.testLastAccessTime_equals_creationTime_afterFirstPut:375 expected:<1623841580000> but was:<0>
[INFO] 
[ERROR] Tests run: 36348, Failures: 1, Errors: 0, Skipped: 988
[INFO] 
[ERROR] There are test failures.

[ufukyilmaz]

Why do we need to set the last access time to a different value from the creation time (why do we need to distinguish them)? Most likely, this is because of some existing optimization in the record impl, but I couldn't understand it.

[ahmetmircik]

@ufukyilmaz it is to distinguish last-access-time from creation-time. Creating a record doesn't mean it has been accessed. We want to keep this distinction not to break backward behavioral compatibility.