Migrate from @ungap/structured-clone to native structuredClone

[alexmuller]

structuredClone is available natively in Node.js 17+. This means that the earliest we can use it would be when we drop support for Node.js 16. See #490 for when @rowanmanning suggested this.

What problem does this feature solve?

Removes the need for a 3rd party dependency to implement structuredClone.

Ideal solution

Remove all the uses of @ungap/structured-clone and replace them with native structuredClone.

Alternatives

We could leave the dependency in place.

[rowanmanning]

We should be able to work on this in mid-August when we drop support for Node.js 16 across our packages.

[rowanmanning]

We no longer use @ungap/structured-clone, we switched to Lodash deepClone to address #623. We may still be able to switch to native structuredClone though, it's worth trying and seeing if the tests pass. If not then we'll have to stick with Lodash.

[Nazehs]

@rowanmanning With Node 18 in use, do we still require lodash? I believe we could eliminate it and adopt a native implementation for deep cloning. This would allow us to reduce third-party dependencies.

[rowanmanning]

Yep we might be able to! I haven't had time to experiment with it yet but I'm hopeful that structuredClone should be enough. It'd be nice to be able to remove lodash