[msbuild] Use the fully resolved path when computing the relative pat…

…h for the LogicalName property. Fixes #20330. (#20364)

This fixes an issue where we'd compute a LogicalName property that was outside
of the app bundle, resulting in broken resources in the app bundle (in
particular the app icon would be missing).

So instead of something like this:

    LogicalName: ../../../../../../../../../tmp/testapp/obj/Debug/net8.0-ios/iossimulator-arm64/actool/bundle/Assets.car

we'll now get:

    LogicalName: Assets.car

and the icons will be correctly embedded in the app bundle.

Fixes #20330.

msbuild/Xamarin.MacDev.Tasks/Tasks/ACTool.cs

@@ -165,11 +165,12 @@ IEnumerable<ITaskItem> GetCompiledBundleResources (PDictionary output, string in
 					if (path.EndsWith ("partial-info.plist", StringComparison.Ordinal))
 						continue;
 
-					var vpath = PathUtils.AbsoluteToRelative (pwd, PathUtils.ResolveSymbolicLinks (path));
+					var resolvedPath = PathUtils.ResolveSymbolicLinks (path);
+					var vpath = PathUtils.AbsoluteToRelative (pwd, resolvedPath);
 					var item = new TaskItem (vpath);
 
 					// Note: the intermediate bundle dir functions as a top-level bundle dir
-					var logicalName = PathUtils.AbsoluteToRelative (intermediateBundleDir, path);
+					var logicalName = PathUtils.AbsoluteToRelative (intermediateBundleDir, resolvedPath);
 
 					if (logicalName.StartsWith ("../OnDemandResources/", StringComparison.Ordinal)) {
 						logicalName = logicalName.Substring (3);