Handle duplicate env error / unique key constraint issue

[jackkav]

changelog(Fixes): Fixed an issue where importing would sometimes result in a duplicate environment error / unique key constraint issue

Motivation
trying to import collections and getting unique key id violation error

the error occurs when find env line returns empty and reruns ensure children
ensure children run getOrCreateForParentId which should get the base env but instead attempts to create a new base env which because its id is derived from the parentId throws the unique key error

this change so far may not fix the issue but it should raise the reproducability.

Closes INS-2269
Closes #5617 #5677

[filfreire]

@jackkav this still doesn't fix it, but I have a simple repro path:

• Create a collection A
• Export collection to file, like fromA.yaml
• Create a collection B
• Import fromA.yaml inside collection B

Happens regardless if the export is of collection or entire workspace - that collection than becomes damaged always.

Throws the error folks are mentioning in #5617

[jackkav]

Might be worth making an e2e test to cover this case for after we fix it.

[lipecss]

im still getting this