Version information is not handled properly in case of clustered setup

When the NiFi runs in clustered mode, the already filled "statusLocation" is being removed from the version information after creation.

• During adding a flow from registry (creating a process group from the standpoint of NiFi) we do enrich the version control information with storageLocation in order to be able to be reload it from registry in case it will be part of a nested structure
• This information is being added, but in case of multiple nodes, the information loses afterward

It looks like, the storageLocation is empty at in thee flow.xml and flow.json and also it is not stored in the internal representation. Single node environments do not suffer from this.

The input check for enriching version information with storageLocation needed a final adjustment.