Machine users can be orphaned during Connection creation

[cheesegrits]

When creating a Connection with a Machine User, it is possible to create the MU (and associated integration) in (CO)TAK, and then never actually create the Connection (ie. navigate away without hitting Save Connection), leaving the MU & integration "orphaned" in COTAK/TAK.

Speaking to some of the WFTAK gang, I'm pretty sure this accounts for several orphaned MU's I was trying to reconcile against ETL.

I'm not sure how we can mitigate this, except maybe a 'beforeUnload' event handler on the ConnectionEdit component?

I've gone some way to mitigating in PR #438, where I'm setting the integration as inactive when it gets created during the MU creation, and only setting it active when the integration is updated after the ETL connection is actually created. That way in COTAK we can filter for inactive integrations and manually garbage collect them periocially. But it would be nice if they got cleaned up from CloudTAK.