[Package Issue]: Logitech.LGS mismatched scopes between versions

Nobody has claimed this yet.

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Installation issue.

### Brief description of your issue

https://github.com/microsoft/winget-pkgs/tree/master/manifests/l/Logitech/LGS

In the 2 recorded versions of Logitech Gaming Software in winget-pkgs; there is a conflict between one version of the app being in machine context; and the newer one in user context.

As a result, the user context one appears to occasionally trip up on installation; especially as the installer is expected to be installed in the machine context.

### Steps to reproduce

https://github.com/microsoft/winget-pkgs/blob/master/manifests/l/Logitech/LGS/9.04.28/Logitech.LGS.installer.yaml

https://github.com/microsoft/winget-pkgs/blob/master/manifests/l/Logitech/LGS/9.04.49/Logitech.LGS.installer.yaml

### Actual behavior

When trying to deploy the software centrally, the user scope entry in winget causes preparation scripts to trip up and not launch & run correctly.

### Expected behavior

Both package versions should have the same scope the installer expects; which reasonably seems to be machine.

### Environment

```raw
N/A deployment is via Robopack/IntuneWin and not winget directly.
```

### Screenshots and Logs

_No response_

Compare manifests/l/Logitech/LGS/9.04.28/Logitech.LGS.installer.yaml and manifests/l/Logitech/LGS/9.04.49/Logitech.LGS.installer.yaml, starting with their installer scope settings. Update the mismatched scope so both versions match the expected machine context, then validate the manifests using the repository's standard checks. Done means centralized deployment no longer encounters a scope mismatch.

Written by the indexing model from the issue text.