v12 integrations: list the technologies we already receive through syslog, NetFlow and the agent, each with a setup guide

[kryonsx]

Owner: @AndresTK89

Why

Many products already send logs to UTMStack v12 through channels we support today:

• any device that can send syslog to the UTMStack Collector;
• any router, switch or firewall that can export NetFlow or IPFIX to the Collector;
• any Windows application that writes to an event log channel the agent already reads (SQL Server, for example, writes failed logins and service events to the Application log);
• any Linux service that writes to the system journal (or to syslog on the host), which the agent streams in full.

Customers can't see this. The Integrations page lists only the 33 built-in integrations, so someone running SQL Server, IIS, Nginx or a Ubiquiti gateway concludes we don't support it. Listing these technologies, each with a card and a short guide that explains how its logs reach UTMStack, needs no new parser and no new collector code. It is mostly list entries, icons, text and one reusable guide per channel. The research behind it covers 95 technologies (25 syslog devices, 25 Windows applications, 25 Linux services, 20 NetFlow exporters), each rated "works today", "works after a setting", "partly" or "needs an agent change first".

What adding one technology means

1. An entry in the guide-only list that names its channel (syslog, netflow, wineventlog or linux). Not a catalog row: the catalog allows one row per data type, and the Windows and Linux agents already own theirs. v12 integrations: groundwork for guide-only integrations (guide list, card names, View logs, syslog guide fix, templates) #2732 sets up the list.
2. An icon and a category in frontend/src/features/integrations/constants/systemModules.ts, with the icon file in frontend/public/integrations/.
3. A name, a one-line description and the guide text in all seven language files (frontend/src/shared/i18n/locales/{en,es,pt,fr,de,it,ru}.json).
4. A guide registered with registerCollector under frontend/src/features/integrations/components/setup/collector/collectors/, built from the shared templates in v12 integrations: groundwork for guide-only integrations (guide list, card names, View logs, syslog guide fix, templates) #2732. In plain words it says: what the product logs, which channel carries it, the exact setting to turn on, and how to check the logs arrived.
5. A "View logs" link that opens the Log Explorer filtered to that technology (each list gives the filter).

Be honest in every guide about what the customer gets: their logs, stored and searchable, and the alert rules that already cover the channel. They do not get vendor-specific fields or a vendor dashboard until someone writes a parser for that product. Where a list says "partly" or "needs an agent change", the guide says so plainly.

Sub-issues

• v12 integrations: groundwork for guide-only integrations (guide list, card names, View logs, syslog guide fix, templates) #2732: groundwork shared by all four lists (do first)
• v12 integrations: guides for devices that send syslog #2733: devices that send syslog
• v12 integrations: guides for Windows applications the agent already collects #2734: Windows applications (SQL Server, IIS and others)
• v12 integrations: guides for Linux services the agent already collects #2735: Linux services
• v12 integrations: guides for devices that export NetFlow or IPFIX #2736: devices that export NetFlow or IPFIX

Each list is ordered by value to customers and has one checkbox per technology, so you can ship them one at a time. Turn a checkbox into its own issue if it grows.