Import a flow containing a subflow without unintentionally creating a duplicate subflow

[knolleary]

To repeat what I said in your other topic about this:

@knolleary

There is a plan to do a better job of this in the future - to let the user choose whether to import it as a copy, use the existing subflow definition, or replace the existing definition with the one being imported.