feat(test): migrate unity test project for unity-cli

[akiojin]

Summary

• This PR adds a full Unity test project under UnityCliBridge/TestProject so unity-cli can validate bridge behavior without depending on the legacy repository.
• It updates the test project package linkage to com.akiojin.unity-cli-bridge so runtime and editor code is exercised through the current package path.
• It introduces small compatibility wrappers for legacy UnityMCPServer.* namespace references so migrated scenes and scripts continue to compile while transitioning to UnityCliBridge.*.

Changes

• UnityCliBridge/TestProject/**: added migrated Unity project assets, ProjectSettings, and package manifest for local reproducible Editor and E2E testing.
• UnityCliBridge/TestProject/Packages/manifest.json: added com.akiojin.unity-cli-bridge with file:../../Packages/unity-cli-bridge reference.
• UnityCliBridge/Packages/unity-cli-bridge/Runtime/IMGUI/LegacyMcpImguiControlRegistry.cs: added runtime compatibility bridge from UnityMCPServer.Runtime.IMGUI to UnityCliBridge.Runtime.IMGUI.
• UnityCliBridge/Packages/unity-cli-bridge/Editor/Helpers/LegacyDebouncedAssetRefresh.cs: added editor helper compatibility bridge for legacy namespace calls.
• UnityCliBridge/Packages/unity-cli-bridge/Editor/Settings/LegacyUnityMcpServerProjectSettings.cs: added settings compatibility type for existing serialized project settings.
• UnityCliBridge/TestProject/Assets/Editor/UpmSigning/UpmPackSigner.cs: switched default package path to Packages/unity-cli-bridge.
• docs/development.md and README.md: documented the new Unity test project location and batch EditMode test command.

Testing

• cargo fmt --all -- --check - passes with no formatting diffs.
• cargo clippy --all-targets --all-features -- -D warnings - passes with no warnings.
• cargo test --all-targets --all-features - passes (23 passed, 0 failed).
• dotnet test lsp/Server.Tests.csproj - N/A in this environment because dotnet is not installed.

Related Issues / Links

• Unity実機E2Eテストを整備しCIで回帰を検出する #2
• [Tracking] unity-cli移行後フォローアップタスク一覧 #8
• unity-mcp-serverベースラインとの差分をMCP→CLI/スキル移行に限定する #11
• feat(migration): migrate mcp-to-cli assets and handover flow unity-mcp-server#389

Checklist

• Tests added/updated
• Lint/format passed (cargo clippy, cargo fmt, svelte-check) - svelte-check N/A: no Svelte sources in this repository.
• Documentation updated (if user-facing change)
• Migration/backfill plan included (if schema/data change) - N/A: no schema or data migration in this PR.
• CHANGELOG impact considered (breaking change flagged in commit)

Context

• The migration tracker identified that unity-cli lacked a full Unity test project with ProjectSettings, which blocked end-to-end Unity validation from being self-contained.
• This PR moves the required test project footprint into unity-cli and keeps compatibility shims so migration can proceed without immediate scene or script rewrites.

Risk / Impact

• Affected areas: repository size, Unity project import time in CI and local environments, and compatibility behavior for legacy namespaces.
• Rollback plan: revert commit dc07a2b to remove the test project and compatibility wrappers.

Notes

• Base branch is main because develop does not exist in akiojin/unity-cli.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/test-project-migration

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}