Update export preset options overrides before doing "Remote Debug"

[dsnopek]

When doing an export any other way, it's already updating the export preset options before doing it.

For example, via the "Export PCK/ZIP..." or "Export Project..." buttons:

godot/editor/export/project_export.cpp

Line 1312 in d33da79

current->update_value_overrides();

Or, via the "Export All..." button:

godot/editor/export/project_export.cpp

Line 1365 in d33da79

preset->update_value_overrides();

But before this PR, it's not doing it before export when using the "Remote Debug" button (aka "One click deploy"). If you've got an export plugin that sets overrides that depend on project or editor settings, this will mean that your settings won't be in effect when using the "Remote Debug" button.

This PR fixes that!

[bruvzg]

It's always done for export, but with some export plugins start_run_native can trigger actions that not involve export (like, starting/stopping server). It's probably still OK to update preset in these cases.

[dsnopek]

It's always done for export, but with some export plugins start_run_native can trigger actions that not involve export (like, starting/stopping server). It's probably still OK to update preset in these cases.

Yeah, it should be harmless: it's just looping over EditorExportPlugins and updating a Dictionary.

However, if any actions get values from the preset - even if they don't do an export - it would still be important to update the options overrides. I don't see any cases of that at the moment, but EditorExportPlatform::run() is passed the preset, so folks writing code in there are going to assume that the preset has all the correct option values on it.

[Repiteo]

Thanks!