Resource can be loaded from cache when changed, cache busting ID not changed if jar files are not updated

In CMS7-8052 cache-busting is optimized to only change the anti-cache ID when a timestamp of a jar file in the WEBINF/lib folder is changed. This introduces the risk that a resource is updated and deployed without changes in the WEB-INF/lib folder. The browser will use the cached version instead of the updated instance.

Work around is to touch a webapp jar file to trigger a new hash.

Solution could be to generate the key build-time or scan all resources