Fix report rendering, table controls, and export data preservation

[PrzemyslawKlys]

Reports lose export headers when column filters are placed at the top, Excel can round long identifiers, and several rendering paths mishandle quoted strings or script delimiters. This change corrects those paths and adds explicit controls for export scope and portable Markdown images.

• Keep semantic headers and saved column searches, including scrolling tables and view-mode changes. Add named search-pane columns and independent title/name alignment.
• Preserve long numeric Excel values and named text columns. Quote CSV fields, protect formula-like text by default, and expose -RawData for programmatic consumers. Add Automatic, All, Filtered, and Selected export scopes.
• Preserve caller-owned arrays and dates, evaluate inline conditions against excluded helper properties, and support multiple grouping levels with independent collapse state and responsive details.
• Initialize tables in nested tabs and revealed containers; support tab deep links, keyboard navigation, and configured top-menu destinations.
• Preserve script data in charts and widgets. Keep Markdown code samples intact while embedding local images, preserve path casing, and parse text links with nested parentheses.
• Validate the checked-in manifest in CI without regenerating or pushing dependency changes.

Related issues: #509, #477, #434, #413, #363, #345, #336, #252, #251, #227, #200, #129.

Dependencies and bundled vendor assets are unchanged, including ApexCharts and the DataTables stack. CSV consumers that require formula-like values unchanged can use New-TableButtonCSV -RawData; relative Markdown image references can be retained with -EmbedImages $false.

Validation: 58 tests pass on Windows PowerShell 5.1, PowerShell 7, and Ubuntu PowerShell 7. Browser checks cover actual Excel/CSV output, filter restoration, scrolling/view switching, nested navigation, grouping/responsive details, Markdown embedding, and script-boundary data. The merged module imports in both Windows runtimes and retains the existing exports and vendor assets. One independent local review and one targeted confirmation were completed; all validated findings are addressed.