Not to change zk node for the partition/table to be deleted when replica is offline

### Search before asking

- [x] I searched in the [issues](https://github.com/alibaba/fluss/issues) and found nothing similar.

### Fluss version

0.6.0 (latest release)

### Please describe the bug 🐞

When the table/partition is deleted, we'll go through the code of handle replica to offline, kicking the replica from isr and elect a new leader. But we can emit the code path for deleted table/partitions.

### Solution

_No response_

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

No file or test is named. Start by tracing the replica-offline handling path described in the issue, including ISR removal and leader election, and check how deleted tables or partitions are represented before the zk node is changed. Done means deletion bypasses that path without changing the deleted table or partition's zk node, with regression coverage.

Written by the indexing model from the issue text.