Productivity tuning

Better, easier & more flexible control of which GDB to use and where to
place windows

Change-Id: I7a2f046067cb4c558f49f27cd3625c0e0492dd8f
gdb.tap.sh reworked

Two reasons:

Accommodate read-line and history using nc and rlwrap (two reals gems in the
jungle of modern day crap).

Aiming for full transparency. gdb.tap.sh should eventually just be able to
be linked to for a fully functional wrapper of another tcp_tap)-able program.

Change-Id: I3af1b79b3460a889ccf85025f72d220d13dd35de
Added sample profile

Will end up in ~/bin/ as usual for s3 dot-files.
Can either be linked to or copied from into ~/ as template.

Change-Id: Id5354c72497b74b11fe871fe7274e5cda4aac02b
Added support for tcp_taps new TCP_TAP_NICNAME

tcp_tap's TAP_LOG_NAME adds much better ability to control incoming
socket-binds. That was part of a bug-fix, but a very nice side-effect is
that security can be moderated, from accepting only 127.0.0.1 (impossible
for outsiders to spoof) into "@ANY@", "@HOSTNAME@" or specific name, each
which their particular use-cases. Small fix did all that (this message is
actually much longer)

Additionally:
* Changes in profile-names
* Log-format change. Contains also PID now, should more then one sessions
  run.

Note: there is now a new hight-level log. It's low traffic and can be left
on. It also defaults to /tmp/something (i.e. will be cleared upon restart).
File-name is controlled via profile-files, but nothing is printed until
profiles are read which is why it works. Filename for this log is controlled
by env-var TAP_LOG_NAME.

Change-Id: I70705f2a73b46a22caea65b7f32bc270735e4de0
Added first lines of nc and rlwrapper code

What beautiful pieces of code they are! Remote session now works almost as
well as if it would be a native GDB session. That with practically *no
change to tcp_tap at all*! Somewhat different than with a real gdb-session
but now much. This really made an enormous difference and it proves me right
not to add that functionality to tcp_tap. It would only have have made it
more complicated and bloated with non-generic code. Also as a side-effect:
It would had made it more GDB  specific (which I don't want).

Having both screen, rlwrapper and nc as helpers give:

* Infinite scroll-back [screen]
* Copy&paste from either your's, the GUI's or other users (sessions) into
  your own execution [screen]
* Memorizing other session users operations into your own history [screen] +
  [rlwrapper].
* Memory of history even across sessions (great!) [rlwapper/readline]
* Potential TAB fill-out. Need to research this more [rlwapper/readline]
* Acting on signals as they were intended to [nc]. No special secret command
  needed any more to exit group sessions. Just ^C and you're done.

nc and rlwrapper now completely replace telnet and is from now-on the
preferred method of connection. This commit contains a fullback to telnet if
both of these aren't installed on your system however. Will write a small
client using these for remote users as well.

Transparency is King(k)!

Additionally:
* Corrected bug about handling local IF's (that's what the diffs about, the
  above is just me rambling about at a late hour with a glass of wine to
  celebrate :))

Change-Id: Ida8f46346513769fc5e841119bf9db95008ef192