Sensitive dynamic properties referencing parameters are not preserved during export/import

Consider an InvokeHTTP processor with a dynamic property set as sensitive and referencing a sensitive parameter:

Authorization => #{myBearer}

When exporting the flow definition, the reference to the sensitive parameter won't be preserved. We'll only see something like:

"Authorization":{"name":"Authorization","displayName":"Authorization","identifiesControllerService":false,"sensitive":true,"dynamic":true} 

When importing the flow definition, the InvokeHTTP instance won't have the dynamic property. The processor will still be showing as valid and, depending on the endpoint, could be running without throwing errors even though the data would not be retrieved from the endpoint as the bearer would be missing.

This is breaking flow deployment and can be hard to figure out when it happens.

(this probably affects 1.x as well)

Since the dynamic property is referencing a sensitive parameter we should preserve the reference when exporting the flow definition.