developer_attribute_initialize: one tab per attribute

The interface is now a tabbed multiparm like Developer Panel's, with
each tab labelled by its attribute name and carrying the attribute's
own type, source, initial value, variation and metadata (range and age
toggles). The chain of attribcreate, switch and attribute SOPs is
replaced by two wrangles that loop over the tabs: one on points for the
values and ages, one on detail for the <attr>_info dictionaries.
Channel names are built at runtime and Houdini still tracks them, so
editing or adding a tab recooks the node.

Existing instances lose their single-attribute parameters on update and
need their tab filled in again; the age toggles are age0_#, age1_# and
age2_# so the tab number does not run into the age number.

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

 ...galante.developer_attribute_initialize.1.0.hdalc | Bin 12636 -> 10934 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/otls/sop_lsgalante.developer_attribute_initialize.1.0.hdalc b/otls/sop_lsgalante.developer_attribute_initialize.1.0.hdalc
index 31d4b51..f307821 100644
Binary files a/otls/sop_lsgalante.developer_attribute_initialize.1.0.hdalc and b/otls/sop_lsgalante.developer_attribute_initialize.1.0.hdalc differ