fix(cache): catch Throwable in CacheManage static init (#1724)

[HandSonic]

Problem

静态初始化器仅捕获了 Exception，而遗漏了诸如
NoClassDefFoundError 之类的 Errors。一旦初始化因 Error 失败，该类
就会被永久“污染”，且缓存会被静默禁用。

此外，还需在 fuzzyDelete() 中添加初始化保护机制，以防止在缓存初始化
失败且从外部调用 fuzzyDelete 时发生 NPE。

Fix

在 开头添加 守卫

Related

Fixes #1724

[openai0229]

The fuzzyDelete() initialization guard looks correct. However, please narrow the catch (Throwable) clause. Catching every Throwable also swallows errors such as OutOfMemoryError, StackOverflowError, and ThreadDeath, after which the application should not continue as if only the optional cache failed. If the goal is to handle NoClassDefFoundError, use a targeted clause such as catch (Exception | LinkageError e) or catch (Exception | NoClassDefFoundError e). The original StateTransitionException shown in the referenced historical issue is already covered by Exception in the current code, so a current-version reproduction or focused test for the intended Error path would also help validate this change.

[HandSonic]

Fixed. Changed to , and added an guard at the beginning of to prevent accessing when cache is not initialized.

[HandSonic]

Fixed. Changed catch (Throwable e) to catch (Exception | LinkageError e), and added an if (!init) return; guard at the beginning of fuzzyDelete() to prevent accessing cacheManager when cache is not initialized.