feat(#5179): invalidate SNAPSHOT cache on every build with Janitor

[volodya-lombrozo]

Invalidates the local SNAPSHOT cache on every build to prevent stale generated files from referencing removed classes.

Fixes #5179

[volodya-lombrozo]

In other words, I suggest invalidate cache in the 1.0-SNAPSHOT each time we have a fresh build. It's a bit better than disabling cache at all, but of course not so fast with the plain cache. But with the janitor we won't have problems with stale cache anymore.

Build	Time
Current branch (Janitor)	4m 48s
master (cache enabled)	3m 40s
master (cache disabled, -Deo.cacheEnabled=false)	5m 14s

[github-actions]

🚀 Performance Analysis

All benchmarks are within the acceptable range. No critical degradation detected (threshold is 100%). Please refer to the detailed report for more information.

Click to see the detailed report

Test	Base Score	PR Score	Change	% Change	Unit	Mode
benchmarks.XmirBench.xmirToEO	18651.332	18777.913	126.580	0.68%	ms/op	Average Time

⚠️ Performance loss: benchmarks.XmirBench.xmirToEO is slower by 126.580 ms/op (0.68%)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[0crat]

@volodya-lombrozo Hey! Nice work on that contribution! 🎉 You snagged +12 points this time: started with the standard +16 points but had to dock -4 since you hit 367 hits-of-code (anything over 100 gets penalized). Pro tip: try to keep those contributions smaller and more focused - you'll avoid the penalty and likely get better reviews! Your running score is looking solid at +397, and don't forget to peek at your Zerocracy account for the latest updates.