Missing rules when using expirable maps/caches from popular open source libraries

首先定位仓库中与 SnapStart 相关警告对应的 Java 规则定义和测试。检查各项检查如何识别库和方法的使用，然后覆盖 Guava expireAfterAccess/expireAfterWrite 以及 ExpiringMap 的过期变体。完成标准是相关的可过期缓存模式会产生警告，同时非过期缓存的使用不受影响。

In case the expirable cache is initialized in the constructor of the Lambda class and some entries are put as well it may happen that the entries are not there anymore after the SnapStart snapshot is restored. The should be a warning of usage of time-based cached with the SnapStart is enabled.

In particular I'm thinking of the usage of 2 popular open source libraries:

• Google Guava ( artifact id guava and group id com.google.guava) and the code like this

myCache = CacheBuilder.newBuilder().expireAfterAccess(3600, TimeUnit.SECONDS) .build();
myCache.put("key", "value");

• Using artifact id expiringmap and the group id net.jodah and the code like this

expiredMap = ExpiringMap.builder().expiration(3600, TimeUnit.SECONDS).build();
expiredMap.put("key", "value");

I know that it's difficult to spot such use cases because both open source libraries offer standard and not expirable caches. But the invocation of the methods like CacheBuilder.newBuilder().expireAfterAccess/expireAfterWrite or multiple variations of methods ExpiringMap.builder().expiration* when creating the cache using these open source tools is a clear indication of the creation of expirable cache.