[codex] Fix non-AI adapter publish metadata

[ifanatics-media]

What changed

Adds publishConfig metadata to non-AI adapter/package manifests that already publish only dist but still use the workspace-local main: ./src/index.ts field during development.

This intentionally excludes packages/ai/*, which are covered separately in #448, and covers the remaining package families such as affiliates, bots, bridges, cloud, DNS, entity, promo, social, targets, VCS, W3C, and webhooks.

Why

These packages build compiled JS and declarations into dist and publish only dist, but without publish metadata a packed package manifest keeps main: ./src/index.ts. That can make published packages resolve a TypeScript source path instead of the compiled runtime artifact.

With publishConfig, pnpm rewrites the packed manifest to expose:

• main: ./dist/index.js
• types: ./dist/index.d.ts
• exports["."].import: ./dist/index.js

Validation

• corepack pnpm --filter @profullstack/sh1pt-bot-core typecheck
• corepack pnpm --filter @profullstack/sh1pt-target-pkg-npm typecheck
• corepack pnpm --filter @profullstack/sh1pt-automation-stagehand typecheck
• corepack pnpm --filter @profullstack/sh1pt-bot-core build
• corepack pnpm --filter @profullstack/sh1pt-target-pkg-npm build
• corepack pnpm pack --pack-destination $env:TEMP/sh1pt-pack-check from packages/bots/core and packages/targets/pkg-npm, then inspected package/package.json and tarball file lists.