Mark auto-install correctly when installing from .ckan file

[HebaruSan]

Problem

If you install a module from a .ckan file, its dependencies will be marked as manually installed instead of auto-installed (see #2753).

Cause

When installing from the mod list, we use ComputeChangeSetFromModList to calculate the change set to display, but ComputeUserChangeSet generates the change set to install, so ModuleInstaller.InstallList can determine which modules were selected by the user:

CKAN/GUI/Main.cs

Line 707 in 91c5bf4

full_change_set = await mainModList.ComputeChangeSetFromModList(registry, user_change_set, module_installer, CurrentInstance.VersionCriteria());

CKAN/GUI/MainChangeset.cs

Lines 140 to 145 in 74ff9af

	installWorker.RunWorkerAsync(
	new KeyValuePair<List<ModChange>, RelationshipResolverOptions>(
	mainModList.ComputeUserChangeSet(RegistryManager.Instance(Main.Instance.CurrentInstance).registry).ToList(),
	RelationshipResolver.DependsOnlyOpts()
	)
	);

However, when installing from a .ckan file, we pass ComputeChangeSetFromModList's change set as if it was selected by the user:

CKAN/GUI/MainInstall.cs

Lines 51 to 68 in 74ff9af

	List<ModChange> fullChangeSet = new List<ModChange>(
	await mainModList.ComputeChangeSetFromModList(
	registry,
	initialChangeSet,
	ModuleInstaller.GetInstance(CurrentInstance, Manager.Cache, GUI.user),
	CurrentInstance.VersionCriteria()
	)
	);
	if (fullChangeSet != null && fullChangeSet.Count > 0)
	{
	// Resolve the provides relationships in the dependencies
	installWorker.RunWorkerAsync(
	new KeyValuePair<List<ModChange>, RelationshipResolverOptions>(
	fullChangeSet,
	install_ops
	)
	);
	}

This makes ModuleInstaller.InstallList think that the user selected them all manually.

Changes

Now we only pass the module from the .ckan file in the change set, so the dependencies can be marked as auto-installed. A few other minor changes are made along the way

• List instead of HashSet since we need a List in the end anyway
• The install options are generated by RelationshipResolver.DependsOnlyOpts() instead of RelationshipResolver.DefaultOpts() with modifications after the fact, for consistency with other installation codepaths

Fixes #2792.

[DasSkelett]

Works great