draft: router rule delivery integration

[xiaobaicai66695]

Purpose

This Draft PR keeps the complete Admin router-rule delivery chain on one branch for final end-to-end validation. Please review the implementation in the child PRs below rather than reviewing this aggregate diff.

Review order

1. Part 1 — existing Condition/Tag delivery chain
2. Part 2 — Affinity/Script Admin backend and configuration-center delivery
3. Part 3 — rule-management UI and Condition v3.1 editing

The child PRs are hosted in the contributor fork and form a dependency chain in the order above.

Integration boundary

Together, the child PRs cover Admin rule modeling, Console APIs, YAML encoding/decoding, ZooKeeper/Nacos delivery and readback, and the traffic-rule UI.

This PR does not change dubbo-go RouterChain, router factory registration, or provider-selection logic. Dynamic Config v3 runtime parsing/matching is handled separately in apache/dubbo-go#3660.

Validation

• Part 1 focused Go tests passed.
• Part 2 focused backend packages passed. The aggregate pkg/console test needs the embedded frontend dist directory, which is unavailable in the isolated split worktree.
• Part 3 frontend tests passed: 9 files / 18 tests.
• The top child branch is code-equivalent to this integration branch for all committed Admin changes.

After the child PRs are reviewed, this branch will be used for the final Admin → configuration center → dubbo-go E2E check.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[xiaobaicai66695]

Closing this draft because the router-rule changes will be reorganized into smaller fork-internal PRs based on feature/router-rule-integration for easier review before submitting to apache/develop.