developer_float_migrate: both methods push values along the vector

Each method now only picks one target point per point, and a shared
pair of wrangles moves the value: send_amount works out Influence times
the value (scaled by the Multiplier attribute and the similarity bias),
transfer subtracts what was sent and adds what arrived via
findattribval on the target. A spike moves one cell per step at full
influence and the total is conserved up to the final clamp. Before,
both methods averaged the values behind each point, so a spike was
diluted to a fifth on the first step and Connectivity mostly blurred.

Proximity picks the nearest point to the position Distance edge lengths
along the vector; on a point cloud, which has no edge length, it uses
the spacing to the nearest neighbour instead of collapsing to zero.
Connectivity picks the point within Depth rings lying most squarely
along the vector, and Depth now defaults to 1 since 0 samples nothing.

The Normal SOP that added an unused N to the output is gone, the
trailing Attribute Delete removes the working attributes instead of a
nonexistent targetmeshsize, and the Multiplier parameters are read for
the first time. Help text added.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

 .../sop_lsgalante.developer_float_migrate.1.1.hdalc | Bin 13763 -> 15151 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/otls/sop_lsgalante.developer_float_migrate.1.1.hdalc b/otls/sop_lsgalante.developer_float_migrate.1.1.hdalc
index 9f7720d..dbcafbf 100644
Binary files a/otls/sop_lsgalante.developer_float_migrate.1.1.hdalc and b/otls/sop_lsgalante.developer_float_migrate.1.1.hdalc differ