There is no point in runner.sh depending on the generated Geany
executable, and this breaks running `make distcheck` before building
the sources, as the Geany executable doesn't exist yet.

These are way too few changes from me over a one-year period :(.

My previous fix (e1ce9cfb) didn't fix all possible use cases (opening
files from CLI when starting Geany). This one should close the gap.

This seems necessary with newer gcc versions to not
require libgcc*.dll libraries on runtime.

Updated Hungarian translation

When quitting, we still have to destroy the Scintilla widget to avoid
any possibility for us to receive signals from it after we destroyed
the associated editor and/or document (used in signal handlers).

I myself don't suffer from the issue, but it is theoretically possible
for Scintilla to emit signals anytime before it is destroyed, so it is
safer like this anyway.  And an user on IRC suffered from crashes on
quit because of this issue, so it seems to actually happen in some
situations.

On Windows we need to change the working directory on startup to not
lock the directory Geany was started from (bug #2626124).
However we can't change the directory to late in the startup process
otherwise plugins maybe unable to load resources from the installation
directory.

Though we also can't change it too early otherwise opening files given
with relative paths in Geany from the command line won't work anymore
(bug #3613096).

This change should fix both issues by changing the working directory after
command line file handling happened and before plugins will be loaded.

Although the strings were properly marked for translation, they weren't
actually translated because they missed run-time replacement.

Update nl.po

First contrib in Github