Branded migration might migrate the wrong profile

[TheOneRing]

Migration from 2.4 might have failed in 2.8.
This resulted in a new configuration used in 2.8.

In 2.9 we fixed the migration, but we migrate the abandoned 2.4 config to 2.9 instead of the 2.8.

This only happened with branded clients, due to the change in the config location in the update from 2.8 to 2.9.

[gabi18]

2.4.3 config from AppData\Local\ownCloud Tespilot Edition
testpilotcloud.zip
2.8.2 config from AppData\Roaming\ownCloud Tespilot Edition
testpilotcloud.zip

[gabi18]

Prerequisite: update testpilot 2.4.3 to 2.8.2

-> result: 2.4.2 config file in AppData\Local, 2.8.2 config file in AppData\Roaming (see #9224 (comment))
-> VFS is ON for 2.8.2

-> and also 2 db-files (which is not relevant here)

Tested update testpilot 2.8.2 VFS ON to testpilotcloud-2.9.2-rc5:

-> confirmed that the correct profile (config file) is taken for migration, VFS remains ON

The config file written to AppData\Roaming\testpilotcloud:
testpilotcloud.zip

[gabi18]

Confirmed fixed with testpilotcloud-2.9.2-rc5.6114.x64.msi.