[CCR][FE Binlog] DROP admission depends on local config cache and diverges across frontends

## Problem

[CCR][FE Binlog] DROP admission depends on local config cache and diverges across frontends

## Minimal reproduction path

Run a frontend cluster with table-level CCR Binlog enabled. Exercise DROP admission with a warm configuration cache, a cold cache, and after a leader change, then compare the dropped-table metadata and Binlog events on all frontends. Verify that the result is determined by persisted configuration, not local cache state.

## Expected result

DROP admission and metadata Binlog output are identical across cache states and frontends.

## Source

This report is a sanitized tracking record for Jira DORIS-28087. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.

Start with the minimal reproduction path: run a frontend cluster with table-level CCR Binlog enabled and exercise DROP admission with warm and cold configuration caches and after a leader change. Compare dropped-table metadata and Binlog events across frontends; done means admission and metadata output are identical and determined by persisted configuration rather than local cache state.

Written by the indexing model from the issue text.