SIG-diagram.svg out of sync with sigs.yaml working groups

SIG-diagram.svg shows 5 working groups that don't have a corresponding entry under `workinggroups:` in sigs.yaml:

- [Structured Logging](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/SIG-diagram.svg#L108-L110)
- [AI Conformance](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/SIG-diagram.svg#L112-L114)
- [AI Integration](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/SIG-diagram.svg#L119-L121)
- [LTS](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/SIG-diagram.svg#L123-L124)
- [Serving](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/SIG-diagram.svg#L143-L144)

Checked against the [`workinggroups:` list in sigs.yaml](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/sigs.yaml#L3544-L3942) with:

```
$ grep -n "^ - dir: wg-" sigs.yaml
3545: - dir: wg-ai-gateway
3598: - dir: wg-batch
3655: - dir: wg-checkpoint-restore
3708: - dir: wg-data-protection
3745: - dir: wg-device-management
3797: - dir: wg-etcd-operator
3848: - dir: wg-node-lifecycle
3894: - dir: wg-workload-aware-scheduling
```

None of the 5 groups above are in that list.

**_(Note: sigs.yaml also lists [`wg-workload-aware-scheduling`](https://github.com/kubernetes/community/blob/e6d1cbd0ca50e350877253d1564bbefffc2fad66/sigs.yaml#L3894), which isn't drawn in the diagram)_**

cc. @dims @wendy-ha

Compare SIG-diagram.svg with the workinggroups section of sigs.yaml, starting with the listed working-group entries and the diagram links in the issue. Determine which list is authoritative, then make the two files consistent and verify that every working group appears in the intended place without introducing other discrepancies.

Written by the indexing model from the issue text.