InternalExpirationManager.entryExpiredInMemoryFromIteration() is currently implemented to either:

• Synchronously remove the expired entry in local caches
• Skip the expiration check and return expired transient (max-idle) entries in clustered caches

The local cache (ExpirationManagerImpl) implementation is perhaps useful to speed up repeated iterations over the cache, but the downside is that it will block to wait for store removals.

The clustered cache (ClusteredExpirationManagerImpl implementation was needed back when confirming the expiration status of an entry required a RPC, but that is no longer the case.

We can just remove entryExpiredInMemoryFromIteration() and any calls to it from the iterators, and it should only break tests that make assumptions about the expiration implementation.