buildNetworkNote is declared in the types but exported from no entry point

[WiktorStarczewski]

buildNetworkNote is declared in the shipped types and implemented in JS, but exported from neither entry point, so no consumer can import it.

Symptom
import { buildNetworkNote } from "@miden-sdk/miden-sdk" fails to link, while tsc accepts it: api-types.d.ts declares export declare function buildNetworkNote(opts: NetworkNoteOptions): Note and dist/*/index.d.ts ships that declaration.

Where it stands

• Implemented at crates/web-client/js/standalone.js:121.
• Not re-exported by crates/web-client/js/index.js (browser/lazy) or crates/web-client/js/node-index.js (the "node" condition).
• Nothing in the repo imports it, so it has never worked rather than regressing.

Expected
Either export it from both entries, or drop the declaration if network notes are meant to be built another way (transactions already exposes the network-note paths).

Note
crates/web-client/js/__tests__/entry-parity.test.js gates the related failure (a helper exported from one entry but not the other, which is what the shared .d.ts makes a runtime break). It deliberately skips the exported-from-neither case, which is this issue; the skip references this number.

[kutluhaneth46]

Taking this. Will export buildNetworkNote from both the browser and node entry points so the shipped types match what consumers can import.