ID 507281 - [Versions] Changing version on an unlinked track item can select the incorrect version

Problem summary
This bug occurs when versioning up or down on an unlinked track item in a way which triggers scanning for new versions. 

For example, if the user selects 'Version Up' but the track item is already at the highest known version it will start a scan (unless this behavior is disabled in the preferences). Then if there is a new version higher than the current one it should move to that, but will instead move to the next version on the (not linked) clip bin item.

Customer reported version
N/A
 

Customer reported platform
N/A
 

Steps to reproduce

1) Launch Hiero/Nuke Studio

2) Load the attached hrox file. The project contains a clip in the bin on v031, and a clip in the timeline on v050.

3) Select the clip in the timeline.

4) Trigger a 'Version Up' from the context menu (right click > Version > Version Up) or with the Alt+Up hotkey.

5) This should trigger version scanning, then try to go to the next available version (which in this case doesn't exist because it's already at the maximum one)
 

Expected behaviour
The clip on the timeline should stay at v050.
 

Actual behaviour
The version will jump from v050 to v031. This is the next version for the clip in the bin.
 

Workaround
The user can manually trigger a scan (right click > Version > Scan For Versions) then select the correct version.
 

Reproduced by support
This bug has been reproduced in:

Nuke Studio 13.2v1 - Windows 10 - Linux CentOS 7

Nuke Studio 12.1v1 - Windows 10 - Linux CentOS 7

Earliest version tested
Nuke 12.2v1
- The version linking functionality did not exist before this version