Upgrading from a navigator that did not assign consistent source ids to a version that does assign consistent source ids causes a build storm on first scan

This affects only Organization Folders.

The first time they are scanned - after upgrade - all the SCMSource implementations will be given new permanent IDs rather than getting a random ID with every scan.

As an ID change triggers a rebuild, the result is a build storm of all branches in all repositories in the organization folder.