feat(changelogs,ui): SBOM-driven chips, Dakota placeholder, pipewire/…

[castrojo]

…flatpak, driver foil cards

• Add pipewire and flatpak to SBOM extraction pipeline (fetch-github-sbom.js)
• Add pipewire and flatpak fields to PackageVersions type (sbom.ts)
• Add pipewire and flatpak to CHIP_TO_SBOM mapping in FirehoseFeed.tsx
• Add enrichLtsFromHistory() to carry forward systemd/bootc/pipewire/flatpak versions for LTS releases that lack direct SBOM data
• Add Dakota placeholder card (BuildStream junction pins, no SBOM pipeline)
• Add GDX package row (Nvidia/CUDA) to OsReleaseCard for LTS stream
• Add flatpak to HEADER_CHIP_NAMES in OsReleaseCard
• Extract kernel/mesa/gnome versions in fetch-github-driver-versions.js
• Add foil card effects (gold/silver gradients) for major/minor driver version bumps
• Add GNOME and Mesa bump tags to DriverVersionsCatalog with destructured variables
• Add sourceText/sourceClass helpers and statsRow to ImagesCatalog showing pulls count, downloads source, and metadata source indicators

Closes #57 (partial), #66, #70, #81

[gemini-code-assist]

Code Review

This pull request refactors the Firehose feed filtering logic, replacing the "showOsReleases" toggle with a "showEverything" option and updating the display logic to conditionally show app updates alongside OS releases. It also introduces specific styling for app entries in the feed. Feedback was provided regarding the "appSectionHint" text, which can be misleading when specific package type filters are active because it may incorrectly suggest that OS releases are still being displayed.

[gemini-code-assist]

The appSectionHint text is misleading when a specific packageType filter (like 'Flathub' or 'Homebrew') is active. In those cases, filteredOsStreamEvents returns an empty array (per line 468), meaning OS releases are hidden, yet the hint still claims they are included. Consider adjusting the hint to reflect the active filter state.