Add more info to `_resources` entries

[schogges]

Description

With kumahq/kuma-gui#4683 the GUI is implementing a generic resources page that gives the user an overview and some linking to all the resources. We would like to provide the user with some additional features and also hide several things:

1. *Insight resources shall be hidden. Would it be possible to have a flag, i.e. isInsight on *Insight-resources, i.e. MeshInsight?
2. Categories: We would like to give the user the opportunity to filter the resources by categories, i.e. security, observability, ... For now we do this on the client side, but for the future if a new resource is added it would be great if there was also category added on the the new resource. I'd propose to use categories because a resource might match to multiple categories. Currently I am using categories: ['security', 'traffic', 'observability', 'performance', 'reliability']

[slonka]

triage: Let's get @justindavies approve the categories. Probably will be in the type descriptor. For 1 - should be straightforward.

[schogges]

Ideally the source of truth would be the openapi specs.
And another thing is that we also don't want to show *Secret resources (GlobalSecret) which would not be covered if we only use isInsight. Probably better to find a flag that is more generic and that we can reuse for different resources that we don't want to show in the GUI.

[justindavies]

Resilience

MeshCircuitBreaker — protects against cascading failures by limiting connections and ejecting unhealthy endpoints
MeshRetry — automatic retry with backoff for transient failures (HTTP, gRPC, TCP)
MeshTimeout — connection, idle, and request timeouts to prevent hanging
MeshHealthCheck — active probing (TCP/HTTP/gRPC) to remove unhealthy instances from load balancing
MeshRateLimit — local rate limiting to protect services from being overwhelmed

Traffic Management

MeshHTTPRoute — advanced HTTP routing: path matching, header rules, redirects, rewrites, mirroring, weighted splits
MeshTCPRoute — TCP traffic splitting and weighted routing (canary/blue-green)
MeshLoadBalancingStrategy — load balancing algorithms (round-robin, least-request, ring hash, maglev), locality awareness, zone failover
MeshPassthrough — controls egress to external services; allow/deny by domain, IP, or CIDR

Security

MeshTrafficPermission — service-to-service access control; allow/deny by identity with shadow mode
MeshTLS — mTLS enforcement, TLS version/cipher configuration, strict vs permissive mode

Observability

MeshAccessLog — request/response logging to file, TCP, or OpenTelemetry backends
MeshMetric — Prometheus/OpenTelemetry metrics scraping and export
MeshTrace — distributed tracing to Zipkin, Datadog, or OpenTelemetry with sampling and custom tags

Testing & Chaos Engineering

MeshFaultInjection — injects delays, aborts, and bandwidth limits to validate failure handling

Advanced / Customisation

MeshProxyPatch — low-level Envoy xDS patches for clusters, listeners, filters, and virtual hosts beyond what standard policies support