[BUG] WebSocket `registerMetaData` field is dead — metadata always registered despite default `false`

- Severity: Medium
- Location:
`shenyu-client/shenyu-client-websocket/shenyu-client-spring-websocket/src/main/java/org/apache/shenyu/client/spring/websocket/annotation/ShenyuSpringWebSocketClient.java:75`; `.../annotation/ShenyuServerEndpoint.java:80`; `.../init/SpringWebSocketClientEventListener.java:167-182` (`handleClass`)
-
Description:
`ShenyuSpringWebSocketClient` and `ShenyuServerEndpoint` declare `boolean registerMetaData() default false;`. The new autoconfig path consumes this for SpringMvc (`ShenyuSpringMvcClientProcessorImpl.java:44-45`, `SpringMvcApiMetaRegister.java:137-138`, `MateDataApiRegistrarImpl.java:141`), but WebSocket has no processor/extractor in the new register path, and the legacy `SpringWebSocketClientEventListener.handleClass` unconditionally calls `getPublisher().publishEvent(metaData)` for every method without ever reading `registerMetaData`.
-
Impact:
The default `false` signals "do not register metadata", yet metadata is published on every refresh. Users cannot opt out of metadata registration for websocket endpoints; the annotation contract is unimplemented.
-
Suggested fix:
Gate `handleClass` metadata publishing on `beanShenyuClient.registerMetaData()` (and for `@ShenyuServerEndpoint`, read the aliased `registerMetaData`).
-
Confidence: High

---
_Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/06-medium-tiers.md`](docs/scan2-2026-08-02/06-medium-tiers.md)._

Start with ShenyuSpringWebSocketClient.java:75 and ShenyuServerEndpoint.java:80, then read SpringWebSocketClientEventListener.handleClass around lines 167-182. Trace how each annotation exposes registerMetaData and verify that metadata publication follows its value for both annotations, including the default false case.

Written by the indexing model from the issue text.