[Pika-Yalei]

Summary

Display Enterprise or Community beside the existing bottom-left version number in both the normal workspace and SQL workspace. The edition follows features.ENTERPRISE_EDITION from the existing global settings response, with loading, retry, and reconnect handling.

• Discover only classes annotated with @Plugin, so the shared EnterprisePlugin interface is not mistaken for a plugin entry. Keep the existing JAR loading and Binder registration flow.
• Keep the integration guide (docs/guides/private-plugins.md) and edition-difference regression workflows in the companion private plugin repository.
• Include the requested Console database and Sidecar development configuration updates.

Companion plugin implementation: https://github.com/ClouGence/open-cdm-plugin/pull/1. It provides the shared plugin API, edition marker, and local install/remove scripts; integrate both changes together. Encryption and signature verification are outside the current implementation.

Related Issues

None.

Test Plan (Required)

• Not tested (explain why below)
• Unit tests
• Integration tests
• Frontend lint / build
• Backend build
• Manual verification

Details:

• Java formatting completed successfully; plugin-loader and SDK tests passed (6 tests). Console, Sidecar, and Alone compilation passed.
• Frontend lint, i18n checks, and unit tests passed (2 suites, 8 tests). Full packaging and the required Web build passed.
• Directed checks passed for capability-request failure and retry, WebSocket initialization recovery, page lifecycle, and stale responses. Existing plugin discovery was checked against deployed JARs.
• Installed the companion plugin using build_plugins.sh, restarted separate Console and Sidecar processes, and confirmed Enterprise in both workspaces. Removed it using remove_plugins.sh, restarted both processes, and confirmed Community.
• Runtime plugin counts changed from 99 installed to 98 removed. Sidecar remained ONLINE, with no plugin or driver loading failures. Refresh and reconnect were verified without browser errors.
• The final running state is Community. The two configuration files were included in a separate follow-up commit at the user's request; their values were used during the split-process runtime validation.

Checklist

• The PR title clearly describes the change.
• The change follows the repository coding standards.
• Documentation was updated when behavior or usage changed.
• Tests were added or updated for behavior changes.
• I confirmed that generated files, dependency directories, logs, and local build artifacts are not included.