fix(windows): handle multiple Python interpreters in Resolve-ODSHostAgentPython

[IronicRayquaza]

Summary

On dev machines with multiple Python executables on PATH (venv + global
install + Microsoft Store alias), Get-Command returns an array instead
of a single ApplicationInfo object. Accessing .Source directly on that
array throws ParameterBindingArgumentTransformationException, crashing
the installer at Phase 07.

Closes #1654

Changes

• ods/installers/windows/phases/07-devtools.ps1 — wrapped both
  Get-Command calls in @() inside Resolve-ODSHostAgentPython so .Source
  is always accessed on a single object per iteration
• ods/installers/windows/ods.ps1 — applied the identical fix to the
  same function (noted but not patched by the reporter)

Testing

• bash -n passes on all changed files
• PSScriptAnalyzer passes with PSScriptAnalyzerSettings.psd1
• Verified fix covers both active installer and ods.ps1

[Lightheartdevs]

Thanks for fixing the Windows host-agent Python resolver in both the install-time and post-install paths; that is the right scope for the multiple-interpreter failure.

Advisory status: looks merge-ready

What looks good:

• ods/installers/windows/phases/07-devtools.ps1 and ods/installers/windows/ods.ps1 both enumerate Get-Command results before reading .Source, so multiple python/py command hits no longer turn into an array-property failure.
• The existing candidate order and deduping behavior are preserved, keeping the resolver change narrow.

What I checked:

• Reviewed the diff and compared both Resolve-ODSHostAgentPython copies.
• Parsed ods/installers/windows/phases/07-devtools.ps1 and ods/installers/windows/ods.ps1 with Windows PowerShell's parser successfully.
• gh pr checks 1665 reports no checks for this branch, so I did not have a full Windows install simulation to lean on.

Thanks again for covering both active resolver copies.