queryClientConfig is merged shallowly, dropping NostrApp's own defaults

`NostrApp` merges the caller's config with a shallow spread
(`src/lib/components/NostrApp.svelte:31`):

```ts
$: mergedQueryClientConfig = { ...defaultQueryClientConfig, ...queryClientConfig };
```

`defaultOptions` is a single key, so any caller that passes

```svelte

```

replaces the whole `defaultOptions` object and silently loses nosvelte's
`staleTime` and `refetchInterval`.

Every test in this repository passes exactly that shape, which is why the
interaction between the library's defaults and a caller-supplied config is
currently untested.

Determined by code reading.

## Direction

Merge `defaultOptions.queries` (and the sibling option groups) rather than
`defaultOptions` as a whole.

Start in src/lib/components/NostrApp.svelte:31 and inspect how mergedQueryClientConfig combines defaultQueryClientConfig with queryClientConfig. Run the repository tests, add coverage for a caller-supplied defaultOptions.queries configuration, and verify that the caller's retry setting is applied while nosvelte's staleTime and refetchInterval remain present.

由索引模型根据 Issue 内容生成。