Server should handle the case of table_id inconsistent between table node and partition node

### Search before asking

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

### Motivation

A follow-up of https://github.com/alibaba/fluss/pull/766.

It seems it's hard to guarantee the consistency of table node and partition node. Even with #766, there is still possible happen a partition node is created by AutoPartitionManager under a re-created table node.

We need to handle this in server side for
1. ListPartition RPC: should filter out the partitions not match the table id
2. Metadata RPC: should filter our the partition metadata that not match the table id
3. CoordinatorEventProcess should handle `CreatePartitionEvent` that the partition is not match the table id and maybe drop the dirty partition node.

### Solution

_No response_

### Anything else?

_No response_

### Willingness to contribute

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

Start by tracing the ListPartition RPC, Metadata RPC, and CoordinatorEventProcess handling of CreatePartitionEvent. The issue describes the required behavior: exclude partitions whose table IDs do not match and handle the inconsistent partition node, potentially dropping the dirty node. No specific files or tests are named, so locate the relevant server entry points and existing RPC tests first.

Written by the indexing model from the issue text.