rethink nufo login and creation logic

[adcxyz]

Currently, the NTMI app always creates and starts an MKtl(\nufo),
and expects to be logged into a nufo's standalone access point network.

This startup sequence should support more flexible login:
The nufo firmware will soon try to log into the network "nUFOlogy",
and create its own standalone access point only if nUFOlogy login fails.
Then it sends its ID via osc "/ntmi/ID", name;
when it receives a login mesage, it begins to send to that address.

When this is ready, the NTMI should on startup:

• collect incoming nufo names (osc "/ntmi/ID" message)
• know which nufo name is its own, and send a login message to it;
• only then create and start the MKtl(\nufo) !
• later: check and display whether the network is nUFOlogy,
  or nufo-xxx with xxx being 003, 012 or similar.

[adcxyz]

this depends on update to nufo firmware ...

[adcxyz]

update:

• nUFO MKtl is only created when so defined.
• MKtls can be disconnected via gui: (shift-click device button)
  to avoid nUFO-side state display failures.

Still open and more:

• nufo should be able to send to multiple addresses.
  either by multiple registration,
  or by broadcast - unless that creates too much traffic?