Description of Changes

Introduced a new function, findComponentChildren4, to replace the previous child-collection logic.
The older implementation was matching nodes from unrelated components due to partial string matching, which caused naming collisions and incorrect traversal results.

The new version uses stricter token-based matching and reliably limits the search to nodes that belong to the intended component only.

This prevents accidental inclusion of similarly named nodes such as:

• root_C0_root (actual component)
• ik_hand_root_C0_root (different component but previously matched)

Testing Done

Verified the function on isolated components.

• Tested on complex guides exhibiting the previous failure cases, including components with overlapping name tokens.
• Confirmed that nodes such as root_C0_root no longer incorrectly match nodes from components like ik_hand_root_C0_root.
• Validated that the change eliminates the runaway auto-renaming loop that previously generated dozens of unnecessary index variations.

All tests confirm correct component isolation and stable traversal without unintended matches.