[BUG] Windows grains include extraneous empty strings

[nf-brentsaner]

Description
Aside from being weirdly divergent from other grains in their construction (e.g. on Windows, osrelease_info should probably be a split form of osversion), osrelease_info has extra empty strings.

Setup
N/A

• on-prem machine
• VM (Virtualbox, KVM, etc. please specify)
• VM running on a cloud service, please be explicit and add details
• container (Kubernetes, Docker, containerd, etc. please specify)
• or a combination, please be explicit
• jails if it is FreeBSD
• classic packaging
• onedir packaging
• used bootstrap .MSI to install

Steps to Reproduce the behavior

# salt --out=json 'WIN*' grains.items | grep -Ev '^jid:' | jq '.[] | with_entries(if (.key|test("^(os|lsb)")) then ( {key: .key, value: .value } ) else empty end )'

{
  "os": "Windows",
  "os_family": "Windows",
  "osfullname": "Microsoft Windows Server 2022 Standard",
  "osmanufacturer": "Microsoft Corporation",
  "osrelease": "2022Server",
  "osversion": "10.0.20348",
  "osservicepack": null,
  "osrelease_info": [
    2022,
    ""
  ],
  "osfinger": "Windows-2022Server"
}

{
  "os": "Windows",
  "os_family": "Windows",
  "osfullname": "Microsoft Windows Server 2019 Standard",
  "osmanufacturer": "Microsoft Corporation",
  "osrelease": "2019Server",
  "osversion": "10.0.17763",
  "osservicepack": null,
  "osrelease_info": [
    2019,
    ""
  ],
  "osfinger": "Windows-2019Server"
}

Expected behavior
osrelease_info should not have an empty second element.

Screenshots
N/A

Versions Report
N/A

Additional context
N/A