make semantics of getPrevLinkable / getNextLinkable consistent

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  |yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | TODO

We started using isLinkable for getLinkableChildren, but not for getNext/PrevLinkable. This makes things consistent again.