Bump every @intX dependency and the vendored Interchange set to 0.5.0

Every published `@intx/*` dependency moves `0.3.0` -> `0.5.0`: root
`dependencies` (`@intx/crypto`, `@intx/mail-memory`, `@intx/tools-lsp`,
`@intx/workflow-host`) and `devDependencies` (`@intx/inference-testing`),
plus the published-package entries inside the vendored manifests, so no
`@intx/*` dep resolves to a release older than the vendored source it
sits next to. `workspace:*` entries and the root `overrides` stay as
they are, keeping one type identity per vendored name.

All eleven vendored paths re-sync to upstream `aa7b78ee`, the peel of
tag `v0.5.0`, recorded as a SHA because the released npm metadata ships
an empty `gitHead`. Upstream drift is confined to `packages/types` and
`packages/storage-isogit`; the rest of the release is upstream's own
`version` field, which the `0.2.2` placeholder convention does not
mirror. `store.ts` is the one patched file the drift touches, so it goes
through a three-way merge, and `bun/vendor-patch-diff` prints the same
divergence multiset for every patched tree before and after the sync.

All forty-two entries across the five `PATCHES.md` ledgers re-adjudicate
to KEEP: `loadErrors`, the durable error-seq handling, the `read_file`
paging description and the whole inference patch set are still absent
from `aa7b78ee`. The published `0.5.0` tarballs now export
`buildMessageHeaders`, `createSubstrateMailboxStore` and
`loadWorkflowDirectorRegistryFromClosure`, so the `@intx/mime` and
`@intx/workflow-host` kill conditions are satisfied; the trees stay in
place because retiring them means re-pointing `overrides` at npm, which
is a separate decision.

Author: TheGreatAxios