Improve console binary handling on MacOS installs #3334

When Nmap is installed on Mac using our provided mpkg package, Zenmap, Nmap, Ncat, and Nping all go into the Mac Applications directory. This is perfect for Zenmap, as that is where you would expect it. It has an Nmap icon and you can click to run it. But the nmap, ncat, and nping console apps also end up there. They don't provide an icon and clicking on them does nothing (because they are console apps). So users may install Nmap, click on "nmap", and feel everything is broken. On the bright side, putting these console apps there seems to include them in the default paths so that they can run from a normal terminal window with no extra configuration.

Still, when I search for "nmap" in finder, the first result is the console app from the Applications directory and of course clicking on it does nothing. Users need to know to click Zenmap instead, which is the second option, at least for me.

I'm not sure of the best solution, but this does seem likely to confuse users. We should probably find a way to either give these an icon and make them do something useful when you click on them (open a terminal window? open Zenmap?), or hide them somehow from the GUI (so Zenmap is all people see or at least the most prominent) while still allowing them to work fine from terminal with default setup/path. We should probably look more into what other console apps do about this.