chore: add a log on the parentId set null

[marckong]

Let's measure how many users are impacted by this bug and experiencing the data linking issue.

• adding a error creation upon parentId set null (this should not happen now)
• adding error stack capturing by Sentry

Closes INS-3301

[marckong]

@gatzjames this was a tricky to find the root cause and fix. I currently added a temporary hack around in the database module that is used in both inso-cli and insomnia desktop client. In my opinion, this is not a great architectural choice made. Maybe I am missing out something here, but,

• why is inso-cli relying on NeDB?
• Why is it relying on a persistence?
• Shouldn't the cli tool to be fire and forget if it was designed to be run in the CI/CD pipeline?

This CLI tool and the electron app are so coupled in the current state of the Insomnia. I think we should decouple this as soon as possible, ESPECIALLY, if Insomnia product wants to revamp the testing feature in my opinion.

[marckong]

I added a HACK to bypass this. Please go ahead if you find a better fix on this.

[marckong]

We are adding the sentry log to measure the data loss issue under the pressure, but ideally we should log the case happening here and fire them in batch outside of the database context.

[jackkav]

nedb is required by inso cli because running requests and tests requires reading context from the db, inso also allows you to point it at different db folders. we have yet to find a good high level solution to this, i would advise leaving some breadcrumbs for someone to undo your hack incase it blocks some upgrade or feature in the future

[marckong]

Not sure if there is more thing to give as breadcrumb. Future contributors should be able to learn the context in this PR description and threads with the INS ticket information as well. They can remove the following functions introduced by this PR: assertModelWithParentId(), registerCaptureException()