Cannot reassign same data instances to table when hierarchy is enabled

[mollykreis]

🐛 Bug Report

With the nimble-table, it is expected that you can pass the same array/object instances with modified property values to setData() and have those updates be reflected in the rendered table. This works as expected when hierarchy is not enabled -- in fact, there's a test that verifies this works as expected. However, when hierarchy is enabled (specifically when parentIdFieldName is configured), this does not work. It looks like the issue is that the arrayToTree code path does not ensure a copy of each data record is made in order for TanStack to recognize the change.

💻 Repro or Code Sample

🤔 Expected Behavior

You should be able to write code like this and have the table reflect the changes:

const data= [{ a: 'hello' }];
table.setData(data);
// table renders 'hello'

data[0].a = 'world';
table.setData(data);
// table renders 'world' if parentIdFieldName is not configured
// table still renders 'hello' if parentIdFieldName is configured

😯 Current Behavior

See expected behavior

💁 Possible Solution

The arrayToTree copy code path in the table needs to ensure that a copy of the data records are made so that TanStack recognizes that there was an update to the data.

🔦 Context

🌍 Your Environment

• OS & Device: [e.g. MacOS, iOS, Windows, Linux] on [iPhone 7, PC]
• Browser [e.g. Microsoft Edge, Google Chrome, Apple Safari, Mozilla FireFox]
• Version [e.g. 1.8.0]