IIS install command uses wrong path for FastCGI configuration

[jkeifer]

Currently, the IIS commands generates something like this for the FastCGI command:
C:\Anaconda_x86\envs\ebagis_prod\python.exe|C:\Anaconda_x86\envs\ebagis_prod\Scripts\ebagis winfcgi --pythonpath=C:\Anaconda_x86\envs\ebagis_prod\Scripts\ebagis

But that example actually should be:
C:\Anaconda_x86\envs\ebagis_prod\python.exe|D:\projects\ebagis\production\ebagis_prod\django-ebagis\manage.py winfcgi --pythonpath=D:\projects\ebagis\production\ebagis_prod\django-ebagis

We see the FastCGI command generated on this line:

django-ebagis/ebagis/management/commands/setupiis.py

Line 89 in e1f277f

<add name="FastCGI" path="*" verb="*" modules="FastCgiModule" scriptProcessor="{{ python_interpreter }}|{{ current_script }} winfcgi --pythonpath={{ project_dir }}" resourceType="Unspecified" requireAccess="Script" />

The current_script and project_directory are created with the assumption the current process is run under the local manage.py, but we are running under the ebagis command. While this assumption is really not valid nor safe, it is reasonable enough given typical usage. Therefore, I think the manage.py ultimately called by the ebagis command needs to replace sys.argv[0] with itself in certain contexts to ensure this commands and others depending on similar mechanisms will not fail like we see in this situation.