fix: publish compiled OpenClaw plugin entry

[RerankerGuo]

Fixes #1675.

Summary

• Point the npm package and OpenClaw manifests at the compiled entrypoint ./dist/index.js instead of index.ts.
• Include dist and tsconfig.json in the published package, and run npm run build during prepublish.
• Compile from the package root so the root OpenClaw plugin entry becomes dist/index.js.
• Align the package type with the existing CommonJS TypeScript output and avoid requiring an unavailable openclaw/plugin-sdk type package at build time.
• Add a package manifest regression test for the compiled entrypoint configuration.

Validation

• node manifest check for package.json, openclaw.plugin.json, and tsconfig.json passed.
• npm pack --dry-run --ignore-scripts --cache /tmp/npm-cache passed and showed package metadata can be packed without the read-only global npm cache.
• Attempted: npm test -- --run tests/package-manifest.test.ts; blocked because vitest is not installed in this worktree.
• Attempted: npm run build; blocked because tsc is not installed in this worktree.
• Attempted: make format; blocked because poetry is not installed in this environment.

[Memtensor-AI]

Automated Test Results: QUEUED

Conflict with dev-v2.0.22 was resolved by merging the base branch into this PR head. Manifest assertions passed locally; cloud test-engine rerun has been queued.

• Run: tr-186b16f3-de9 on cloud test-engine 10011
• Branch tested: refs/pull/2013/head

I will post the final pass/fail result when the run completes.

[Memtensor-AI]

Automated Test Results: PASSED

Cloud test-engine rerun against dev-v2.0.22 completed successfully.

• Run: tr-186b16f3-de9 on cloud test-engine 10011
• memos_local_openclaw/unit: 10 passed, 0 failed, 0 skipped

Manual code review is still required before merge.