fix(examples): Move non-persistent buffers to a valid device

[Eta0]

Non-persistent buffer devices

During deserialization using load_into_module, only the buffers loaded from the deserializer are overwritten on the target module, and any extra buffers on the target module remain unmodified. This can lead to an error if there are existing buffers on the target module that are on a different device from the deserializer, since the model will end up scattered across multiple devices.

This primarily arises as an issue when serializing with include_non_persistent_buffers=False, since non-persistent buffers may be created on any device, and will not be overwritten by the deserializer. In particular, this led to an error when running the code in deserialize.py (which does not expect buffers from anything but the deserializer) on a model serialized using examples/hf_serialization.py (which uses include_non_persistent_buffers=False).

This change adds an extra section to deserialize.py that moves remaining non-persistent buffers to a device matching the deserializer after regular deserialization finishes. It is not included in the speed measurement because non-persistent buffers are explicitly not any business of the deserializer—only of external code—and they can be included and measured by setting include_non_persistent_buffers=True if it is desired to force the deserializer to handle them instead.