useEventList() silently drops everything that is not kind 1

`useEventList(rxNostr, key, ids)` requests the given ids and then filters the
results with `filterTextList()`, which requires `kind === 1`
(`src/lib/stores/operators.ts`). Anything else is discarded without a trace.

Verified on v0.6.1:

```
useEventList(..., ['e-1']) relay answers with a kind-30023 event carrying id 'e-1'
→ status: 'success', data: []
```

`EventList` renders its `nodata` slot, so a caller asking for ids they know
exist sees an empty list and no error.

The behaviour is right for `useTextList`/`TextList`, which is the same function
re-exported under a different name (`useText.ts` does the same for `useEvent`).
It is the name `useEventList` that promises something it doesn't do — and
`useEvent`, its single-event counterpart, has no such kind restriction, so the
pair is inconsistent with itself.

## Deciding what to do

Not obvious enough to just pick:

- Make `useEventList`/`EventList` kind-agnostic (filter by id only) and leave
`useTextList`/`TextList` as the kind-1 wrapper. Matches the names and matches
`useEvent`, but changes what existing `useEventList` callers receive.
- Keep the behaviour and drop the `useEventList` name, leaving only
`useTextList`. Honest, but removes public API.

Either way it is a breaking change for someone, so it wants a minor release
rather than a patch.

Start in src/lib/stores/operators.ts and compare useEventList with the kind-1 filtering used by useTextList; then inspect useText.ts, EventList, and useEvent for the public API relationship. Verify the v0.6.1 behavior with a non-kind-1 event. Done means the API direction is decided, its breaking-change implications are documented, and the affected names behave consistently.

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