Roll filterable, sortable, and limitable into SS_List interface

[maxime-rainville]

Description

Lots of method that expect a list of object will declare that they expect an SS_List. Those methods usually implicitly assume that the list they are provided will be filterable, limitable and sortable.

In theory someone could define their own class that implements SS_List without implementing the Filterable, Sortable, limitable.

We had a long conversation about how to address this in #8609. The conclusion was that fixing this in SS 4 is not possible without introducing ambiguity.

The suggestion from that issue for SS 5 was to:

• rename the current SS_List to Collection and
• introduce a new SS_List that encapsulate Collection, Filterable, Limitable and Sortable.

We've since decided that having the individual Filterable, Limitable, and Sortable interfaces on their own isn't helpful.

Acceptance criteria

• The Filterable, Limitable, and Sortable interfaces are all rolled into SS_List
• SS_List interface is updated to have appriopriate typhints
• SS_List is updated to include and list methods we think should be absolutely included in all lists (e.g. excludeAny() is missing)
• All old references are update in code and in doc
• Changed is called out in upgrade doc

Kitchen Sink CI

• https://github.com/creative-commoners/recipe-kitchen-sink/actions/runs/11512255504

PRs

• API Combine Sortable, Filterable and Limitable into SS_List #11433
• API Use SS_List as type silverstripe-graphql#612
• API Check is instance of SS_List silverstripe-reports#199
• API Check is instance of SS_List symbiote/silverstripe-gridfieldextensions#420
• DOC Update changelog with list interface changes developer-docs#605

[sminnee]

This isn't a bug; the system is working as designed.

[maxime-rainville]

There's a bunch of other problems with List that maybe we want to address while we are looking at CMS5. Just to name a few:

• return types for all the method is not defined
• removeAll is not defined in the interface

[maxime-rainville]

We were just discussing this issue. We are thinking that maybe we don't need Filterable, Limitable and Sortable. It seems like a bit of over engineering since there's literally no implementation of SS_List that doesn't implement those as well.

[maxime-rainville]

Not going to make it to CMS5.

[GuySartorelli]

@emteknetnz I won't merge the PRs yet - you need CMS 5 PRs to deprecate the old interfaces. There's no way to add a notice, but we still need the @deprecated PHPDoc and a changelog entry.