Sort dependencies first in modpacks

[HebaruSan]

Motivation

#3499 sorted the relationships in modpacks alphanumerically by identifier (rather than randomly). There have been some problems with this; since the ordering of a changeset matters, sorting alphanumerically means that dependencies might end up later in the changeset than their depending mods, so for instance there might be cases where a user is prompted to choose a mod and is allowed to pick one that will conflict with a dependency of something later in the changeset.

Changes

Now we use a relationship resolver to sort dependencies before depending mods in modpacks. This way when a new modpack is exported, the ordering will better reflect how the mods should be installed.

Ideally we would also give the user some options for manually reordering mods, but I discovered that WinForms's ListView control cannot do that when item groups are in use. It either puts moved ListViewItems in the wrong place or omits them completely, and if we try rebuilding the entire list from scratch, there is no way to restore the scroll position so you can see the mod you just moved. Perhaps something to come back to in the future if we feel like reimplementing the modpack editor with a different underlying control.

Side fixes

To test this, I tried installing the community lifeboat modpack and found that the scrollbars from #4249 flickered quite a bit. Some calls to SuspendLayout and ResumeLayout are added to improve this.