Update OS options in bug-report.yaml

[RDMacLachlan]

A microsoft employee must use /azp run to validate using the pipelines below.

WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.

For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

[RDMacLachlan]

This is based on the request found in:

• Bug title: The bug template target Windows version is missing versions 26100, 26120, 26200 #5534

[DrusTheAxe]

Line 43-48 PackagingType

• Packaged (MSIX)
• Unpackaged

What if I have I have a not-.msix install and a sparse package with External Location? You're kinda doing both.

"Packaged" vs "Unpackaged" is clear and unambiguous RUNTIME information -- Packaged=process HAS package identity, Unpackaged=process LACKS package identity. But there is no process at install time, and likewise at build-time.

SUGGESTION: Add a 3rd option. What to label it's the question. "Packaged (MSIX Sparse Package and External Location)"?

[RDMacLachlan]

Line 43-48 PackagingType

• Packaged (MSIX)
• Unpackaged

What if I have I have a not-.msix install and a sparse package with External Location? You're kinda doing both.

"Packaged" vs "Unpackaged" is clear and unambiguous RUNTIME information -- Packaged=process HAS package identity, Unpackaged=process LACKS package identity. But there is no process at install time, and likewise at build-time.

SUGGESTION: Add a 3rd option. What to label it's the question. "Packaged (MSIX Sparse Package and External Location)"?

I've added a new entry for "Packaged (Sparse package)"

[riverar]

Why does it take you so long to make edits to this bug form?