im_bounds 1.1: make the min/max attribute names work

The rename and delete nodes acted on sub_val_min and sub_val_max, which
nothing produces, so the Label parms were ignored and the output was
always _<attrib>min and _<attrib>max. They now act on the names the
promote nodes write, so the defaults give P_min and P_max like 1.0 and
turning a toggle off removes the attribute.

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

 otls/sop_lsgalante.im_bounds.1.1.hdalc | Bin 16383 -> 15989 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/otls/sop_lsgalante.im_bounds.1.1.hdalc b/otls/sop_lsgalante.im_bounds.1.1.hdalc
index b9ebc7c..06cd8e6 100644
Binary files a/otls/sop_lsgalante.im_bounds.1.1.hdalc and b/otls/sop_lsgalante.im_bounds.1.1.hdalc differ