It just makes the display more crowded - and does not significantly add
to the information shown.

By prefixing the two main application binaries ("n3n-edge" and
"n3n-supernode") with the name of the project, it makes it clear that
these generic names are associated with a specific project.

This change has been suggested in the past, but was always avoided as it
was a configuration-breaking change.  Since the new n3n release is
making other breaking changes, now is the right time to perform this
rename.

Let the kernel takes care of assigning the port ID of the netlink socket.

The netlink socket id uses the same namespace in all docker containers,
so if the userspace code assigns the nl_pid then there is a possiblity
of a collision, resulting in errors like:
    "Could not bind NETLINK socket: Address already in use [98]"

Cherry-picked from 0df939ed5b0a7013a73f2df78f6a805b5ec555b3 in ntop/n2n#1169

Thanks @sbrodeur