User-unfriendly layout of files at the top level in published builds

There are several issues with the main folder of default BizHawk. On their own they are just minor nitpicks, but together these issues create unnecessary complications that could be easily avoided.

• Main executable is not called BizHawk.exe, but instead EmuHawk.exe.
• Barely any mention of the term "EmuHawk" anywhere, so people aren't sure if opening EmuHawk.exe is correct.
• Multiple .exe files in the main folder. This causes even more confusion, because the tool is not installed with an installer but must be manually extracted.
• .config files are not known by default on Windows, so this is really only minor, but Windows hides file extensions by default, so the folder will appear to have files: DiscoHawk, DiscoHawk.exe (the .config file), EmuHawk, and EmuHawk.exe (the .config file).

All these together cause uncertainty when users run into issues starting the tools. It also adds unnecessary troubleshooting steps for those trying to help.

The problems could be easily mitigated, for example, by renaming the main executable, moving DiscoHawk into a separate folder, and possibly renaming the .config file completely or at least remove the .exe from the config filename.

No source files or tests are named. Start by locating the build or packaging entry point that produces the published top-level folder, then review the proposed executable and folder naming changes with their effect on manual extraction. Done means the published layout clearly identifies the main executable and avoids unnecessary confusion from additional executables or configuration files.