Update logic to check for settings.ini first

[Twincarb]

Updating/Reversing the logic for which settings file to check for, if I am correct we are now using the settings.ini file so it should be checked for before settings.php

removed comments that are repeating the code

edited the error title to be specific on what is missing.

[borpin]

The issue here is that a new system (which will have a settings.ini file), that imports a backup, will then use the wrong settings file as the import of a backup brings across what might be a settings.php file from the system backed up.

What we need is a means of transferring the settings.php to a settings.ini file to complete the migration. Ideally only the settings that are different to the default should be included in the settings.ini file.

Even better would be a means of editing settings from the UI.

For now it should stay as-is.

[Twincarb]

@borpin that does explain why it is the way around that it is, I havent looked to see what is saved in the backup, its possible that the restore script could be made to handle the conversion to settings.ini But that is outside of this PR.

I agree with having the ability of editting of settings in the UI would be handy...