[5.0.2] LCN TM 通知 TC 失败导致数据不一致

### 1. Bug Description

我的业务是 A,B,C三个服务，A 服务作为业务入口，依次调用 B，C 两个服务。

USER -> A
A -> B
A -> C

当TM 通知 B 或者 C commit 的前，如果这两个服务宕机，此时 A 服务并没有捕获到异常。这会导致 USER 已为接口调用成功了。

我不确定是我的用法有问题，还是目前就存在这样的问题。我理解此时用该有一定的重试机制，并且重试失败后此全局事务应该处于挂起状态，并抛出异常给业务。

### 2. Environment:
- JDK version: 1.8
- OS: macOS
- TX-LCN version: 5.0.2

Start by reproducing the A-to-B/C transaction flow described in the issue with TX-LCN 5.0.2, JDK 8, and the stated environment. Trace how the TM handles a participant that is down before commit notification and check whether the observed success response matches the framework's documented behavior. Done means the failure outcome, retry or suspension behavior, and business-facing exception are covered by a verified result.

Vom Indexierungsmodell aus dem Issue-Text verfasst.