[BUG] WSSD Agent Service service will fail to start due a malformed paramater string

**Describe the bug**
A fresh install of either AksEdge-K8s-1.31.5-1.11.247.0.msi or AksEdge-K3s-1.31.6-1.11.247.0.msi will end up with a non starting WSSD Agent Service service

This is due to a malformed parameter string to start the Windows service, where two space characters are present between "wssdagent.exe and" "--service" in the windows Registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wssdagent

ImagePath

C:\AksEdge\wssdagent.exe --service --basedir "C:\ProgramData\wssdagent" --dotfolderpath "C:\ProgramData\wssdagent" --nodeagentfqdn PCWIN11OHA --objectdatastore "registry" --wssdproviderspec hcs

that should become the following with a single place.

C:\AksEdge\wssdagent.exe --service --basedir "C:\ProgramData\wssdagent" --dotfolderpath "C:\ProgramData\wssdagent" --nodeagentfqdn PCWIN11OHA --objectdatastore "registry" --wssdproviderspec hcs

**Quick fix**
Change this registry key and restart the service.

**Root cause and fix**
The msi files for k8s and k3s have the malformed argument string starting with a blank space that should be deleted.

Inspect the MSI definitions for the K8s and K3s packages and trace how they generate the wssdagent ImagePath under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wssdagent. Verify that the generated command has one space before --service, then test a fresh installation to confirm the WSSD Agent Service starts.

Written by the indexing model from the issue text.