fix(ui): retain user input when parsing invalid JSON during import

[TCL735]

Closes #16099

Added a third party library that wraps JSON.parse with linting and detailed error messaging.

For now, we are going to put the detailed error messages into the toast. As @hoorayimhelping mentioned, there is a potential for moving the detailed error message into something more permanent and useful for the user.

[zoesteinkamp]

Outside of my textarea comment everything looks fine to me

[hoorayimhelping]

Great work, thanks for finishing this up! LGTM

1. What are your thoughts on showing the error in the notification toast? When playing with this, I was thinking it might be better to show it in a more permanent and easy to read place. We might want to follow up with design about this, if so.

2. The only other feedback I have is to say that the PR description is a great place to give some context into your thoughts and decisions. For example, I saw that you switched to a library instead of using JSON.parse. I assumed it's cause it gives better failure indications, but I don't know for sure. The PR description is a good place for you, the author to explicitly state anything so there aren't any assumptions made. It's also a good place to put testing instructions and / or gifs / screenshots.

Great work regardless!