Windows jalview_x copies of command line BAT and PS1 launcher and update scripts are not updated through getdown

For command line use.

In the appdir (on Windows and Linux this is the installation folder) is a bin folder with the command line launch scripts:
jalview.sh
jalview.bat
jalview.ps1
(and also the update scripts, update.sh etc).

In linux a symbolic link is made from somewhere appropriate to jalview.sh. The symbolic link could be jalview, jalview_develop, etc.
The symbolic link to update.sh is named update_jalview, update_jalview_develop etc.
In macOS, similarly named symbolic links are made in JalviewX.app/Contents/MacOS and for a system install this path is put in a file in /etc/paths.d.

In Windows, there are no symbolic links and the PATH for the user or system is adjusted by Install4j to add the appdir/bin folder.
So that "jalview_develop" etc is available a copy of jalview.bat and jalview.ps1 to jalview_develop.bat and jalview_develop.ps1 is made (and also the update.bat and update.ps1).

These copies are made at install time, and are not updated in getdown.
They could be in the future.