feat: add support for Ambassador API gateway in provider detection an… - #89

Summary

Two bug fixes and one new provider.

Fix: YAML modal close button unresponsive (IngressDetail, NodeDetail)

IngressDetail and NodeDetail had overflow-y-auto on their root div. When the events tab (IngressDetail) or a long pod/conditions list (NodeDetail) caused the container to scroll, Chromium's hit-test coordinates for any position: fixed child were offset by the scroll amount — so clicking the visually-correct close button registered a miss. Fixed by changing the root to overflow-hidden and placing only scrollable body content inside a flex-1 overflow-y-auto inner wrapper, keeping the fixed modal outside any scroll container. Also added overflow-y-auto to the IngressDetail events tab, which was the only tab missing it (causing the root to actually scroll).

Fix: IngressDetail events tab Refresh button scrolls away

After the overflow fix, the events tab toolbar (header + Refresh button) was inside the scroll region, so it disappeared when the event list was long. Separated the toolbar into a shrink-0 row above a dedicated flex-1 overflow-y-auto event list, matching the pattern other tabs already used.

Feat: Ambassador API gateway provider

Detects Ambassador / Emissary-Ingress via the getambassador.io API group and surfaces four core resource sections in the sidebar: Mappings, Hosts, TLS Contexts, TCP Mappings. Follows the identical pattern used for Istio, Traefik, NGINX Inc, and KEDA — no new abstractions.

Type of change

• Bug fix
• New feature

Checklist

• npm run build passes cleanly
• npm run test passes
• cd go-core && go test ./... passes
• New code includes tests where appropriate
• Docs updated if behaviour changed