im_float_ramp, im_ramp_float: promote and read the same in_min/in_max detail attributes

promote_min wrote in_min and promote_max wrote max, while scale_input
read min/max, so the ramp input was always fit from 0 and the remap
branch read an in_max nothing wrote. Every node now uses in_min/in_max:
the remap wrangle overwrites them so its override reaches scale_input,
and im_delete1 removes both at the end.

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

 otls/sop_lsgalante.im_float_ramp.1.0.hdalc | Bin 9518 -> 9197 bytes
 otls/sop_lsgalante.im_ramp_float.1.0.hdalc | Bin 9443 -> 9118 bytes
 2 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/otls/sop_lsgalante.im_float_ramp.1.0.hdalc b/otls/sop_lsgalante.im_float_ramp.1.0.hdalc
index 26cbc04..8bc63b4 100644
Binary files a/otls/sop_lsgalante.im_float_ramp.1.0.hdalc and b/otls/sop_lsgalante.im_float_ramp.1.0.hdalc differ
diff --git a/otls/sop_lsgalante.im_ramp_float.1.0.hdalc b/otls/sop_lsgalante.im_ramp_float.1.0.hdalc
index a8838a1..7f3b20f 100644
Binary files a/otls/sop_lsgalante.im_ramp_float.1.0.hdalc and b/otls/sop_lsgalante.im_ramp_float.1.0.hdalc differ