fix(solution): use ArgumentList for PAC CLI invocation to fix stray quote on --packagetype

[Copilot]

Compress-DataverseSolutionFile -PackageType Managed fails because PAC CLI receives Managed" (trailing quote) as the --packagetype value, causing an invalid-argument error.

Root Cause

Arguments were built as a single manually-quoted string:

// Fragile — trailing backslash in a directory path breaks Windows arg parsing
var args = $"solution pack --zipfile \"{resolvedOutputPath}\" --folder \"{workingPath}\" --packagetype {PackageType}";

When workingPath ends with \, the sequence "D:\folder\" contains \" which Windows CommandLineToArgvW treats as an escaped quote — the closing " is never seen as a terminator, and --packagetype Managed is absorbed into the folder value. When PAC CLI is invoked through a .cmd wrapper this quoting interaction produces a stray " appended to the final token (Managed").

Changes Made

• PacCliHelper.ExecutePacCliWithOutput signature changed to accept string[] of individual arguments instead of a pre-quoted string string
  • net8.0: populates ProcessStartInfo.ArgumentList — the runtime handles all escaping
  • net462: builds a properly-escaped Arguments string via EscapeWindowsArgument, which correctly doubles trailing backslashes before the closing "
• CompressDataverseSolutionFileCmdlet, ExpandDataverseSolutionFileCmdlet, ImportDataverseSolutionCmdlet, ExportDataverseSolutionCmdlet updated to pass individual unquoted argument tokens

// After — each value passed as a discrete, unescaped token
var pacArgs = new[]
{
    "solution", "pack",
    "--zipfile", resolvedOutputPath,
    "--folder", workingPath,
    "--packagetype", PackageType.ToString()
};
var result = PacCliHelper.ExecutePacCliWithOutput(this, pacArgs);

Testing

• Unit tests pass
• E2E tests pass (if applicable)
• Manual testing completed

Checklist

• Code follows the project's coding conventions
• Documentation updated (if needed)
• Tests added/updated (if needed)
• PR title uses conventional commit format (REQUIRED)