`SoleData` 0.16.9 is on main but 0.16.8 is the newest registered version

`Project.toml` on the default branch declares:

```toml
version = "0.16.9"
```

The Julia General registry's newest entry for `SoleData` is **0.16.8**.

So anyone installing through `Pkg` gets 0.16.8, and whatever changed to justify the bump to 0.16.9 is not
reachable that way. The gap is invisible from a git checkout, which is how it tends to persist.

For context, this is not an ecosystem-wide lag: `SoleLogics` (0.13.7), `SoleModels` (0.10.8) and
`ModalDecisionLists` (0.1.0) are each in sync between main and the registry. Three packages have
stalled - this one, and two reported separately in their own repositories.

### What would close it

Tagging the release so the registrator picks it up, or - if the bump was provisional and not meant to
ship yet - nothing at all, in which case this issue can close with that as the answer. Either is
useful to know from outside.

Noticed during an outside survey of the ecosystem.

Check the Project.toml file on the main branch to confirm the version is 0.16.9. Look for any recent commits that might have triggered a version bump. Understand the Julia package registration process, likely using Registrator.jl or similar. The fix is to tag the release correctly so the registry updates, or revert the version in Project.toml if the bump was accidental.

由索引模型根據 Issue 內容生成。