`using Sole` reaches 4 of the 14 ecosystem packages

`Sole.jl` is the ecosystem's front door and its most-starred repository, so it is where most newcomers
arrive. Today it re-exports four packages.

`src/Sole.jl`, in full:

```julia
module Sole

using Reexport

@reexport using SoleBase

@reexport using SoleLogics
@reexport using SoleData
@reexport using SoleModels

using SoleModels: load_arff_dataset

# using SoleFeatures

# using SolePostHoc

end
```

`SoleFeatures` and `SolePostHoc` are commented out. `ModalDecisionTrees`, `ModalDecisionLists`,
`SoleXplorer`, `ModalAssociationRules`, `SoleReasoners`, `SoleDecisionTreeInterface` and `MultiData`
are not mentioned.

So someone who installs `Sole` expecting the ecosystem gets no decision-tree learning, no rule mining,
no post-hoc analysis and no reasoning - several of the things the ecosystem is best at.

**Second, the compat bounds have drifted.** `Project.toml`:

```toml
[compat]
SoleBase = "0.12 - 0.13"
SoleData = "0.15 - 0.16"
SoleLogics = "0.9 - 0.13"
SoleModels = "0.9 - 0.10"
```

Components are at or near the top of those ranges already, so the next minor bump on `SoleLogics` or
`SoleModels` will hold the umbrella back rather than follow it.

### Why raise it now

The components are pushed almost daily; `Sole.jl` was last pushed on 2026-01-07. That asymmetry is
invisible from inside and very visible from outside, and the umbrella is the first thing a newcomer
touches.

### What would close it

Deciding which packages the umbrella is *meant* to re-export - your call, not a bug with an obvious
fix - and then making the file and the bounds say it. If some are deliberately excluded (load time,
heavy dependencies, maturity), saying so in the README would answer the question just as well as
including them.

Happy to prepare a pull request once the intended set is decided.