[Task] Verify independent Java client against main repo admin/bootstrap

### Description

## Background

The split `shenyu-client-java` repository can compile and pass unit tests across multiple JDK versions, but we still need end-to-end verification against ShenYu main repo admin/bootstrap.

This task verifies that the independent client artifacts can register with and be consumed by the main repo runtime.

## Tasks

- [ ] Build or install the latest local `shenyu-client-java` artifacts.
- [ ] Start ShenYu admin from the main repository.
- [ ] Start ShenYu bootstrap from the main repository.
- [ ] Verify Spring MVC client registration.
- [ ] Verify beat heartbeat registration and renewal.
- [ ] Verify discovery instance registration.
- [ ] Verify route data is visible in admin.
- [ ] Verify bootstrap can consume the registered route data.
- [ ] Record any incompatibility between client repo and main repo.

## Optional Tasks

- [ ] Verify Dubbo client registration.
- [ ] Verify gRPC client registration.
- [ ] Verify WebSocket client registration.
- [ ] Verify SOFA/Tars/Motan registration if the local environment supports them.
- [ ] Verify MCP registration through `/shenyu-client/register-mcp`.

## Expected Output

A verification report containing:

- Main repo commit used
- Client repo commit used
- JDK versions used
- Modules verified
- Pass/fail results
- Incompatibilities found
- Logs or screenshots if failures occur

## Acceptance Criteria

- At least Spring MVC registration, beat heartbeat, and discovery registration are verified.
- Any failure includes enough detail to reproduce.
- The result can be used to decide whether the split client baseline is release-ready.

### Task List

_No response_

Start with the shenyu-client-java artifacts and the main repository's admin and bootstrap startup steps. Verify the listed Spring MVC registration, beat heartbeat renewal, discovery registration, route visibility, and bootstrap consumption, then record commits, JDK versions, results, incompatibilities, and reproducible failure logs or screenshots in the verification report.

Written by the indexing model from the issue text.