fix(bytes): replace std::forward<D>(d) with std::move(d) in move constructors

[YuanYuYuan]

Summary

• Replace std::forward<D>(d) with std::move(d) in three Bytes move constructors in bytes.hxx

Root Cause

MSVC 19.44 (VS 2022 17.14, shipped with the ROS 2 buildfarm) rejects the pattern:

auto d = [p = ptr]() mutable { delete p; };
using D = decltype(d);
auto drop = DroppableType::into_context(std::forward<D>(d));  // C2665 / C3536

When D is deduced as decltype(d) — a local lambda type — it is always a non-reference type. std::forward<D>(d) then expects a D&& argument, but MSVC 19.44 refuses to convert the lvalue d to D&&, reporting:

error C2665: 'std::forward': no overloaded function could convert all the argument types
error C3536: 'drop': cannot be used before it is initialized

This is a conformance tightening introduced in a recent MSVC toolset update. Since D is never a reference here, std::forward<D> is semantically identical to std::move. Using std::move(d) is unambiguous and correct on all compilers.

Affected constructors

• Bytes(std::vector<uint8_t, Allocator>&&) — line 71
• Bytes(std::string&&) — line 96
• Bytes(uint8_t*, size_t, Deleter) — line 115

Context

This broke the ROS 2 buildfarm Windows CI when rmw_zenoh_cpp instantiates these constructors. Tracked in the ROS 2 PMC discussion and visible at:
https://ci.ros2.org/job/ci_windows/27547/

The fix is minimal — 3 lines changed, no behavior change on any compiler.

Breaking Changes

None