Consider adding Windows Debug Interface Access (DIA) SDK wrappers for PDB analysis

My only concern with the pdb crate is it doesn't look like it's been updated in awhile. It's probably fine (it has few dependencies by the looks of it) but it makes me slightly wary.

[..] I think long term it would be good to use official debugging APIs on Windows hosts and only fallback to the pdb crate on other platforms (or maybe if they're unavailable for some reason).

-- https://github.com/rust-lang/rust/pull/143669#issuecomment-3057992603

Currently, some run-make tests use llvm-pdbutil to inspect PDB for symbols and other purposes, but operating on llvm-pdbutil's textual output seems rather fragile, as between llvm-pdbutil versions that's not guaranteed to stay the same (there's an pdb2yaml subcommand, but then we're still parsing yaml?).

Consider introducing Windows Debug Interface Access (DIA) API wrappers to perform PDB analysis programmatically via the Officially Recommended ™️ way instead.

Start by reviewing the run-make tests that use llvm-pdbutil and how they consume its textual output. Read the Windows DIA SDK documentation and compare it with the existing PDB analysis needs, including the possible pdb2yaml path. Done means the project has a decided, programmatic approach for PDB analysis rather than relying on fragile llvm-pdbutil output.