feat: route and audit cluster runtime operations by selected instance

[Aias00]

Closes #1243
Closes #1262

Summary

• route Apache cluster discovery, details, and Broker configuration operations through the selected instance endpoint
• propagate the selected instance through Cluster page APIs while preserving legacy callers without instance context
• record structured cluster IDs for cluster and Broker configuration audit entries

Validation

• JAVA_HOME=$(/usr/libexec/java_home -v 21) PATH="$JAVA_HOME/bin:$PATH" mvn -Dtest=ClusterServiceTest,RocketMQBrokerConfigServiceTest,RocketMQClusterProviderTest,AuditServiceTest test
• npm test -- --run src/api/cluster.test.ts src/api/clusterContract.test.ts src/services/clusterService.test.ts
• npm run build

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[RockteMQ-AI]

Summary

Adds instance-aware routing to cluster runtime operations — when an instanceId is provided, admin API calls are routed through RuntimeAdminClientResolver instead of the static NameServer config. Falls back cleanly to legacy behavior when instanceId is absent.

Strengths:

• Backward compatible: all new parameters optional, default methods in ClusterProvider interface
• Clean routing abstraction via RuntimeAdminClientResolver
• Frontend correctly uses ref pattern (selectedInstanceIdRef) to avoid stale closures in async callbacks
• Test mocks properly updated for new constructor dependencies
• Frontend correctly filters to APACHE vendor instances only

One minor observation:

• ClusterService.listClusters(String instanceId) log says "Listing all clusters" without including the instanceId — see inline comment.

Overall a well-structured change. LGTM.

---

Automated review by github-manager-bot

[RockteMQ-AI]

[Info] Minor logging improvement: the log message "Listing all clusters" doesn't include the instanceId parameter. Consider adding it for observability, e.g. log.info("Listing clusters for instance: {}", instanceId) when instanceId is present.

[RockteMQ-AI]

⚠️ Merge conflict detected

This PR has conflicts with the base branch and cannot be merged. Please rebase or merge the base branch into your branch and resolve the conflicts:

git fetch origin
git checkout feat/studio-instance-scoped-cluster-runtime
git rebase origin/main
# resolve conflicts, then:
git push --force-with-lease

This is a one-time reminder. Feel free to @mention me for a re-review after conflicts are resolved.

---

Automated notification by github-manager-bot

[RockteMQ-AI]

Summary

This PR adds instance-aware routing to cluster runtime operations, enabling the dashboard to target specific RocketMQ instances when listing clusters, viewing cluster details, and updating broker configurations. The changes span both backend (controller → service → provider) and frontend (instance selector UI).

Changes reviewed:

• Added instanceId parameter to ClusterController endpoints (listClusters, getCluster) as optional request parameter
• Extended ClusterProvider interface with instance-aware method signatures
• Updated ApacheClusterProvider to resolve cluster discovery and broker config through selected instance endpoint
• Added instance selector component to Cluster page in frontend
• Proper backward compatibility: legacy calls without instanceId retain existing behavior

Assessment:

• ✅ Clean layered architecture: controller → service → provider with proper separation of concerns
• ✅ Backward compatible: optional instanceId parameter with required = false
• ✅ Consistent pattern with other instance-aware operations (Consumer Group, Topic)
• ✅ Frontend integration adds instance selector for user-facing cluster operations
• ✅ Good documentation in PR body with verification steps

LGTM — solid multi-instance support for cluster runtime operations.

---

Automated review by "github-manager-bot"