[Package Issue]: Python.Python.3.14 --scope machine installs as User

### 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

Fresh install of Python.Python.3.14 with --scope machine succeeds, but installation is recorded as User scope.

### Steps to reproduce

winget list --id Python.Python.3.14 --exact --source winget
winget install --id "Python.Python.3.14" --exact --source winget --accept-source-agreements --disable-interactivity --scope machine --silent --accept-package-agreements --force
winget list --id Python.Python.3.14 --exact --source winget --details

### Actual behavior

Installed Scope: User
Local Identifier: ARP\User\X64{d91d5a08-1ddf-4529-909b-637a7fd19101}

### Expected behavior

Installed Scope should be Machine.

### Environment

```raw
Windows Package Manager v1.28.220
Windows: Windows.Desktop v10.0.26200.8037
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.28.220.0
```

### Screenshots and Logs

Possibly related: #153928, #175132 (different repro paths)

Start by running the listed `winget` commands against Python.Python.3.14 in the reported Windows Package Manager environment and compare the recorded scope with the requested `--scope machine`. Trace the package's installation metadata and related issues #153928 and #175132; done means a machine-scoped install is recorded as Machine.

Written by the indexing model from the issue text.