Does broadcast_object_list() still load Tensors in the broadcasted objects to the sender's GPU, or has that been changed?

This was an issue previously, so I tried landing #61539 to add a map_location argument similar to torch.load() to specify which device to load the Tensors in the broadcasted objects. However, since I changed the underlying serialization to use torch.save() / torch.load() instead of pickle.Pickler / pickle.Unpickler, it broke internal workloads and was reverted, where the hypothesis for the breakage was the difference in default pickle protocol level between pickle.Pickle and torch.save().

The ZeRO _broadcast_object() uses torch.save() / torch.load() and uses the map_location argument to avoid loading received Tensors to the sender's GPU.