Fix win32 ARGV0 names

The ARGV0 names of manage-agents and the win32ui needed more clarity.
Using 'ossec-agent' doesn't really makes sense. This will help in
figuring out what is doing what in the log file for example a little
easier.
Merge pull request #111 from awiddersheim/fix_win32_names

Fix win32 ARGV0 names