Nifi flow version control should ignore (unused) remote ports in RPGs

Nifi flow version control is inconsistent in tracking actions for Remote Process Groups

Suggested solution: ignore changes to unused remote ports (i.e. ports that have not been switched on in the "Mange remote ports" dialog.  This also prevents unrelated input/output ports from affecting a version controlled flow.

See below for list of steps to reproduce, note that it creates an inconsistent state between PG1 and PG2

1. start Nifi
2. create "group-a" Process Group (call it PG1)
3. enter PG1
4. add RPG to http://localhost:8080/nifi/ HTTP
5. leave PG1
6. commit changes to flow control
7. add input port "input-a"
8. add funnel
9. add connection "input-a" to funnel
10. start "input-a"
11. enter group-a
12. refresh remote on RPG
13. new port appears when calling "Mange remote ports", no change to version control for PG1
14. drag in new PG, import "group-a" (call it PG2)
15. immediately PG2 detects local change: "Remote Input Port was added"
16. repeat 7-10 to add new Input Port "input-b"
17. no change for PG1
18. PG2 detects local change: "Remote Input Port was added"

The situation is worse if you attempt to commit changes to PG2

1. commit changes to PG2
2. refresh canvas, PG1 will detect new version
3. update PG1 to new version
4. PG1 will immediately detects local changes: "Remote Input Port was added/removed"