v12- fix(forwarder): preserve HTTP/HTTPS integrations on config sync

[yllada]

What

SyncCollectorConfig was deleting HTTP/HTTPS-only integrations (e.g. github)
on every service restart because they are not present in ProtoPorts.

Why

HTTP integrations like github live only in HTTPPorts and are written to
cfg.Integrations[key].HTTPS by EnableHTTPIntegration. The sync loop checked
only ProtoPorts for known keys, so on the next boot it treated github as
obsolete and removed it — silently losing the enabled integration.

Fix

Added a guard in the cleanup loop to skip deletion when the integration entry
has an active HTTP or HTTPS pointer. Those entries are owned by
enable-integration / disable-integration and must not be touched by sync.

[github-actions]

🛑 AI review — Blocking issues

One or more high/critical issues can break things and must be fixed before merging. Details below.

⚠️ architecture (gemini-3-flash-lite) — non-blocking warnings

Summary: Logic change in SyncCollectorConfig prevents removal of HTTP/HTTPS integrations; minor formatting changes included.

• medium collectors/forwarder/collector/config.go:58 — Hardcoding logic to skip deletion of HTTP/HTTPS integrations in SyncCollectorConfig may lead to orphaned configurations. Ensure this logic is consistent with the global collector lifecycle management.

🛑 bugs (gemini-3-flash-lite) — blocking — must fix before merge

Summary: Concurrent map iteration modification bug and potential nil pointer dereference in SyncCollectorConfig

• critical collectors/forwarder/collector/config.go:56 — Concurrent map modification: deleting from 'cnf.Integrations' while iterating over it using 'for key := range cnf.Integrations' will cause a runtime panic in Go.
• high collectors/forwarder/collector/config.go:57 — Potential nil pointer dereference: 'cnf.Integrations[key]' is accessed before checking if the key exists in the map, which could lead to a panic if the map state is inconsistent.

✅ security (gemini-3-flash-lite) — clean

Summary: The diff contains only minor logic adjustments to configuration synchronization and whitespace/formatting changes; no security vulnerabilities identified.

No findings.

[utmstackprapprover]

Changes requested — AI review found blocking issues (high/critical, or engineer review required). See above.