fix: remove merge-deep from the validation

[Megapixel99]

We used to use merge-deep to assign parameters to a new object; however, we can use structuredClone to do the same thing and remove the dependency on merge-deep. structuredClone only works on node 17+ but node 16 reached EOL in September 2023 per https://endoflife.date/nodejs and https://nodejs.org/en/blog/announcements/nodejs16-eol.

[Megapixel99]

Ran the tests locally with all of the same versions as below (and 23), all of the tests passed (except for node 16).

Versions used to test:

• v23.0.0 (passed)
• v22.10.0 (passed)
• v20.18.0 (passed)
• v18.20.4 (passed)
• v16.20.2 (failed)

[enov]

Great PR! merge-deep is unnecessary nowadays and has some require magic conflicting with some js bundlers. I pulled the branch and tests against Node.js v18, v20, and v22 were successful.

[Megapixel99]

The tests are failing due to a newer version of path-to-regexp being used. I will install the newer version and update the tests

[Megapixel99]

The tests are failing due to a newer version of path-to-regexp being used. I will install the newer version and update the tests

I updated all of the dependencies and updated the tests, I can make the changes part of this PR or make a new PR with the changes to the tests. Aside from the changes to package.json and adding onto the tests (just to make sure I did not break anything) only two lines were changed to ensure the tests pass.