chore(admin-ui): migrate to camelCase API in @janssenproject/cedarling_wasm

## Background

PR JanssenProject/jans#14900 renamed the Cedarling WASM binding's exported functions and methods to camelCase. Data fields on result objects were left as-is, so `request_id` and friends do not change.

admin-ui currently pins `@janssenproject/cedarling_wasm@0.0.338`, which predates the rename. Published `0.0.467` carries the new names.

## Scope

Bump the dependency and update the call sites.

- `package.json` — `0.0.338` to `0.0.467`
- `app/cedarling/client/CedarlingClient.ts` — `init_from_archive_bytes` to `initFromArchiveBytes` (import and call), `authorize_multi_issuer` to `authorizeMultiIssuer`
- `__mocks__/@janssenproject/cedarling_wasm.ts` — same two names
- `app/cedarling/__tests__/client/CedarlingClient.test.ts` — same two names

`result.decision` and `result.request_id` stay unchanged.

## Not in scope

`0.0.467` still ships the old flat package layout (`cedarling_wasm.js` and `cedarling_wasm_bg.wasm` at the package root). The new `dist/` build with separate browser, node, cjs and edge entries plus an `exports` map has not published yet, because the `build_cedarling_wasm` nightly job is failing.

That means no bundler changes here. The `optimizeDeps.exclude` entry in `vite.config.ts` and the current wasm loading path both stay. Once the new layout does publish we will need a second pass to re-test bundling, and that belongs in its own issue.

## Acceptance

- `npm run build` passes
- Cedarling tests pass
- Authorization works end to end against a real policy store