frontend: Update Map graph model

[sniok]

GraphNode model is simplified

export type GraphNode = {
  /**
   * Unique ID for this node.
   * If this node represents a kubernetes object
   * then uid of that object is preferred.
   **/
  id: string;
  /** Display label for this node */
  label?: string;
  /** Subtitle for this node */
  subtitle?: string;
  /**
   * If this property is set  then it means this graph Node
   * represents a kubernetes object.
   * Label and subtitle will be set based on the object's name and kind.
   */
  kubeObject?: KubeObject;
  /** A node may contain children Nodes. */
  nodes?: GraphNode[];
  /** A node may containain Edges that connect children Nodes. */
  edges?: GraphEdge[];
  /** Whether this Node is collapsed. Only applies to Nodes that have child Nodes. */
  collapsed?: boolean;
  /** Any custom data */
  data?: any;
};

GraphNode can have label and subtitle or kubeObject

Node	Preview
{ id: "some-node", label: "Node Label" }
{ id: "some-node", label: "Node Label", subtitle: "Node Subtitle" }
{ id: "some-node", label: "Node with an icon", subtitle: "Node Subtitle", icon: <Icon icon="mdi:plus-circle-outline" width="32px" /> }
{ id: pod.metadata.uid, kubeObject: pod }
{ id: "some-node", label: "Node with children", nodes: [...], edges: [...] }

Since any GraphNode now can represent kubernetes object we can have better representation of groups like Namespaces and Nodes

Updated Namespace representation

There's now Icon and when clicking on namespace it shows details

---

A new way of creating edges is introduced called Relation

export interface Relation {
  fromSource: string;
  toSource?: string;
  predicate: (from: GraphNode, to: GraphNode) => boolean;
}

With Relation it's easier to define relationships between nodes. For example here's a definition for relation between Pods and ConfigMaps

const configMapUsedInPods = makeRelation(Pod, ConfigMap, (pod, configMap) =>
  pod.spec.volumes?.find(volume => volume.configMap?.name === configMap.metadata.name)
);

This change also allows to optimize which nodes are loaded. Before if you had ConfigMaps enabled in the Map it would load all Pods to see if there are any connections, even if Pod were deselected from the Map filters.
And now Relations are decoupled from sources and can be called only if both sources are activated.
You can still add edges from a Source if you need to.

---

Improved perfrormance

When I measured performance of the current implementation one thing that was overlooked is GPU load.
During simple things like panning around GPU load was high, causing dropped or partial frames.

Before:

will-change CSS hints allow the engine to dramatically reduce GPU usage
After:

---

Improved Grouping buttons

Now it takes a little less space