Freezing when opening a node with id=0

[uoyniXnaH]

Describe the bug
Thank you for this component. It is great and helps me a lot.
I noticed a small bug that, if a node's id was set to be 0, the treeview could be rendered though, when try opening the node, the page would freeze.

To Reproduce
At the demo 1
If we change the id of node "Folder 1" to be 0, and try opening "Folder 1", the page freezes and does not respond.

Expected behavior
I am not sure. I guess 0 is the parent's id. If a node id is 0, the component may stop rendering to raise an error or something. Freezing is unexpected.

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Chrome/Windows webview 2
• Version: Chrome 143

Additional context
If you are too busy to fix this bug, I am pleased to have a try.

[foul11]

The same thing happens if two nodes have the same ID.
I spent too much time trying to figure this out until I found this issue.

I think I've figured out the reason for this behavior after spending a bit of time in the debugger.
It's that we can accidentally create an infinite loop if an object references itself.
Since it's open, we'll try to children it in the next render cycle, and so on in a loop.
I think the solution to this problem is to issue a warning and break the loop if we see our tree looping on itself.

Test cases that generalizes the above:

const rootId = 0;
const edgeCaseTree = [
    { id: 1, parent: rootId, text: '1_0' },
    { id: 2, parent: 1, text: '2_1' },
    // { id: 1, parent: 2, text: '1_2' }, // If we uncomment, we should expect a warning.
    // { id: rootId, parent: 2, text: '0_2' }, // OR, If we uncomment, we should expect a warning.
    // { id: 1, parent: 1, text: '1_1' }, // OR, If we uncomment, we should expect a warning.
]