fix: change version resolution order to restore legacy file fallback behavior

[nek023]

Summary

Fixed the issue where the order of processing during version resolution was reversed between v0.15 and v0.16.

In v0.15, the lookup was performed in the order of .tool-versions → legacy file.

asdf/lib/utils.bash

Lines 166 to 182 in 31e8c93

	file_name=$(asdf_tool_versions_filename)
	asdf_version=$(parse_asdf_version_file "$search_path/$file_name" "$plugin_name")
	if [ -n "$asdf_version" ]; then
	printf "%s\n" "$asdf_version|$search_path/$file_name"
	return 0
	fi
	for filename in $legacy_filenames; do
	local legacy_version
	legacy_version=$(parse_legacy_version_file "$search_path/$filename" "$plugin_name")
	if [ -n "$legacy_version" ]; then
	printf "%s\n" "$legacy_version|$search_path/$filename"
	return 0
	fi
	done

In v0.16, the lookup order was changed to legacy file → .tool-versions.

asdf/internal/resolve/resolve.go

Lines 59 to 79 in 0146164

	legacyFiles, err := conf.LegacyVersionFile()
	if err != nil {
	return versions, found, err
	}
	if legacyFiles {
	versions, found, err := findVersionsInLegacyFile(plugin, directory)
	if found || err != nil {
	return versions, found, err
	}
	}
	filepath := path.Join(directory, conf.DefaultToolVersionsFilename)
	if _, err = os.Stat(filepath); err == nil {
	versions, found, err := toolversions.FindToolVersions(filepath, plugin.Name)
	if found || err != nil {
	return ToolVersions{Versions: versions, Source: conf.DefaultToolVersionsFilename, Directory: directory}, found, err
	}
	}

The documentation states that setting legacy_version_file = yes enables the behavior: "Use plugin fallback to legacy version files if available."
To ensure fallback works as expected, the lookup order needs to be reverted to the v0.15 behavior.

https://asdf-vm.com/manage/configuration.html#legacy-version-file

Other Information