Add support for multiple nodes running the same release

The extended start script uses the `release name` (instead of the `node name`) when generating the pipe directory for an Erlang node. This prevents users from "deploying" multiple (Erlang) nodes running the same (Erlang) release, which might come in handy in a dev environment.

By using the `node name` instead of the `release name`, one can deploy `{N}` dev nodes locally and still be able to attach to all of them. Currently, one can only attach to the last deployed dev node. The pipe directory of the `{N - 1}` first dev nodes get overwritten.