feat(wrapper-generator): generate remaining OData operation shapes

[Joywambui-maina]

Fixes #

Changes proposed in this pull request

• Generate media/content downloads (78 routes: /content, /logo, /favicon, attachmentsArchive), completing the shape list in WrapperGenerator: generate OData actions, functions, and remaining operation shapes #3709 — every shape it names now emits, compiles and imports
• Stamp each cmdlet with a [GraphRoute(method, path)] attribute so the parity gate reads the operation's route from the compiled assembly instead of reconstructing it from generated C#. Reconstruction is lossy for parameterized functions and wrong for namespace-qualified actions, so the gate had been excluding 1,669 cmdlets from comparison — it now excludes none
• Order Count before the cast suffix on /$count routes, matching the published SDK (Get-MgUserMemberOfCountAsGroup, not …AsGroupCount) — 126 cmdlets
• Drop the -OutFile parameter from content writes whose response is an entity rather than a stream; it was declared but never read on 56 cmdlets
• Collapse three parallel OData segment tables into one, making "named ⟺ emittable" structural rather than a comment asking three tables to stay in sync
• Refresh the generator docs against measured figures

38/38 modules generate and build · 184/184 unit tests · 11,737 cmdlets

Note on diff size: ~76k of the insertions are the derived parity data (parity-input-ledger.v1.0.csv and the three parity-*.json), which are generated and pinned by ParityDataDriftTests. The hand-written code and docs are roughly 2,000 lines.

Depends on: feat/bind-request-body-properties — powershell-v3 doesn't yet have DerivedCollisionResolutions.cs or the collision data this builds on, so a branch based there wouldn't compile. Retarget once the parent merges.