Add producer-backed outpost SDK with ethers v6

[joshglogau]

Summary

Adds @wireio/sdk-outpost as the chain-neutral TypeScript facade over directly importable Ethereum and Solana producer libraries.

• loads and validates caller-supplied deployment profiles for both chains
• exposes typed chain clients through OutpostClient.create(...)
• supports reserve inspection, reserve management, reserve-swap operations, and optional Ethereum BAR node-owner registration
• uses ethers v6 throughout the Ethereum client
• imports producer-owned types, factories, IDLs, runtime data, and manifests directly
• contains no consumer-side artifact generation, handoff download, or generated contract sources

Producer packages

The current branch remains pinned to the public Ethereum 0.2.2 and Solana 0.2.1 packages. The next aligned target is 0.3.0 from these handoff-based producer releases:

• Wire-Network/wire-ethereum#192
• Wire-Network/wire-solana#473

Producer repositories verify and publish the exact checksummed deployment artifacts. SDK-outpost only consumes the resulting npm libraries and composes their manifests for live deployment verification.

Repository integration

• root build and test scripts remain unchanged
• follows the existing TypeScript and hybrid CJS/ESM package flow
• uses sdk-core reserve and Wire-chain primitives rather than duplicating them
• BAR is an optional deployment capability and does not alter reserve/swap behavior when absent
• no TypeChain, ethers v5, consumer generator, package verifier, workspace artifact override, local handoff URL, or custom root build hook

Verification

• repository lint passes
• full repository: 87 suites / 948 tests pass
• latest GitHub Build and Test check passes before this documentation-only update

Remaining release work

1. merge the producer handoff PRs and publish both artifact packages as 0.3.0
2. replace the two npm pins, refresh the frozen lockfile, and rerun SDK verification
3. publish sdk-outpost after platform approval

Staking remains separate follow-up work.

[jglanz]

This NEEDS to be refactored, the generated assets should not be tracked here, instead they should be published artifacts from wire-{ethereum,solana}.

Scripts need to be refactored with zx and moved to the correct repos and under a folder layout beneath scripts/

[joshglogau]

Waiting for Wire-Network/wire-ethereum#176 & Wire-Network/wire-solana#414 before CI built test will pass to be ready for merge

[joshglogau]

Status: SDK implementation and local verification are complete; this PR remains draft. CI is waiting for wire-ethereum#176 and wire-solana#414 to publish their artifact packages, then the frozen lockfile can be refreshed.

Architecture: one generic SDK facade consumes the source-owned ETH/SOL artifacts plus an immutable deployment profile. Client creation verifies the Wire chain ID, Ethereum EIP-1967 implementation/code hashes, and Solana genesis/ProgramData hashes before returning a client. Mutable RPC/explorer endpoints remain in a separate catalog.

Consumer: wire-tools-ts#53

[jglanz]

• pnpmfile.cjs - REVERT -this is the exact thing that caused a MEGA issue!

if (process.env.WIRE_USE_LOCAL_OPP_MODELS === LOCAL_OPP_MODELS_ENABLED) {
  appendLocalOppModelOverrides()
}

• should generate.mjs still be in this repo (and verify)?

• RELEASING.md seems like it should belong in the repo root

• (this one I can accept knowing it can be improved) The OutpostClient shouldn't know about ethereum or solana and should rely instead on a factory pattern

[jglanz]

There are substantive issues, some pre-existing

[jglanz]

nit-pics aside from the generate.mjs and verify-package.mjs being in the wrong repos; having them in wire-libraries-ts is the same as having a verify script for lodash. They are published packages, verification should have happened already

[joshglogau]

Generate and verify originally converted raw producer artifacts in this consumer; both scripts are removed, and the producer packages now publish the directly consumable TypeScript libraries.