Support inline (flow-sequence) arrays

[MariusStorhaug]

Why

YAML supports a compact, JSON-like inline (flow) form for sequences, but the parser currently only understands the block (multi-line, dash-prefixed) form.

What

ConvertFrom-Yaml should parse inline flow sequences, such as:

skills: ["C#", "PowerShell"]

Acceptance criteria

• A mapping value written as a flow sequence parses to the same result as the equivalent block sequence

[MariusStorhaug]

What changed: Reformatted the issue body to the MSXOrg Issue Format — a local Why plus an outcome-level What/acceptance criteria. Removed the Technical Decisions and Implementation Plan sections (and other implementation-tradeoff notes).
Why: Issue bodies should state local purpose and observable outcome without leaking implementation detail into the outcome-level description; durable technical decisions belong in the PR/design, not the tracking issue.
Follow-up: None.