f301dfbb10
Since nodes are not uniquely assigned to zones (some nodes are in two zones at the same time), it's better not to expose this detail in multiple APIs. This avoids having to explain the behavior multiple times. Now one just has to use `get_zone_by_node/socket` and can then use a seperate method to get the zone stack for that zone like before.