Remove legacy session-in/out WASM exports
Four wasm-bindgen free functions survived the migration to the
OpakeContext path and kept shipping in dist/ even though every TS
caller goes through the context methods now:
- proactiveSessionRefresh → opake.proactiveRefresh()
- cleanupExpiredPairRequests → opake.cleanupExpiredPairRequests()
- healStaleGrants → opake.healStaleGrants()
- retryPendingShares → opake.retryPendingSharesViaOpake()
Each took `session_js: JsValue` and threaded the session back through
`result_with_session` — the pre-OpakeContext shape that violated the
WASM security boundary (tokens + DPoP keys serialized into JS memory).
The replacement context methods keep all session material inside WASM
and were already documented as canonical. A contributor who grepped
for e.g. `healStaleGrants` and saw both shapes had no way to tell
which was correct; this deletes the decoy.
Rust-internal helpers that only the legacy path used are deleted too:
- wasm_util::make_client
- wasm_util::result_with_session
- wasm_util::priv_key_from_slice
`pub_key_from_slice` stays (used by the current OpakeContext and
FileManager bindings). The daemon module keeps its constants exports
and `daemonTaskDefs` — those are what the Service Worker and CLI
share agreement on.