Move all sorting to the modeling store, and then all views preserve the sorting

[robertbrignull]

This PR aims to make sorting of methods easier and prevent them from changing sort order and flying around when you make manual changes. Sorting of methods is moved to the modeling store so it happens in one place only, and then it is the job of each view to preserve the ordering of methods it is given.

This gives us a lot more control over what actions trigger a change in method sorting. As of this PR the only actions that should cause methods to change order are:

• the initial loading of methods
• saving modeled methods
• new AI predictions

It also helps reduce some of the code bloat caused by #3382 because we no longer need to pass as much information to all the different views.

Checklist

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[koesie10]

LGTM, but there seem to be a few failing tests dependent on the sorting

[koesie10]

Perhaps name this something like createGroups or groupMethods since we're not actually sorting the methods?

[robertbrignull]

We can't really call it groupMethods because that's also the name of the method in sorting.ts. I've renamed it to createGroups and we can always tweak again in the future if we want to.