Connection profile is not copied somewhere under extension control

[sstone1]

When you create a new connection in VSCode, it remembers the path to the provided connection profile file. If you download a connection profile from IBPv2, put it into your Downloads directory, import it into VSCode, delete the connection profile from your Downloads directory (thinking that you've imported it!), then the connection stops working.

We copy (rather than reference) the certificate and private key files, so you can delete those after importing them. This means that we have a bit of a mixed up story around what we link to and what we copy that is hard to explain.

My vote would be that when you create a connection, it copies the connection profile, so you avoid this problem altogether - but we need to figure out how updating that connection profile would work.