Do others find saturation_move not looping confusing?

[deviantintegral]

I recently discovered that saturation_move does not loop like hue_move does, such as with this device: https://www.zigbee2mqtt.io/devices/8718699703424.html#moving-stepping

This is actually specified in the zigbee specification if you look up "Move saturation command" in https://zigbeealliance.org/wp-content/uploads/2019/12/07-5123-06-zigbee-cluster-library-specification.pdf.

Increase the device’s saturation at the rate given in the Rate field. If the saturation reaches the maximum allowed for the device, stop.

From a high level, I think of hue and saturation as a pair of values, and expect them to behave similarly. I'd been hoping to set my lights to loop through both hue and saturation at different rates. I don't think there's anything in the code to change, but should we update the docs to make this clearer? I'm happy to file a PR, but only if others have had the same confusion as well.