make saving of internal client connection routing optional in project

[http://wayne.in-giro.org/]

i feel that it may be useful to have an option for each application in a project that allows one to decide whether or not LADISH should remember, and thus reconnect, JACK graph connections that a client makes to itself, which i call internal connections (i am assuming that a client is a unique instance in the JACK graph, thus 2 instances of the same application would be 2 separate clients in this case).

for example, Ardour 2.x (like many other JACK apps) uses the JACK graph for all of its internal (and external) routing. thus, a LADISH project file will be filed with all those connections, and will try to maintain those connections, as will Ardour 2.x. however, if there was a way to tell LADISH to only remember external JACK graph connections that an client makes, that would simplify the project file, and probably improve performance, since LADISH/Ardour would not be duplicating each other's effort.

with the new Ardour 3.x internal routing, Ardour 3.x will allow one to use non-JACK routing, achieving a similar result as i am explaining above. however, internal routing is optional. also, there are many apps which will continue to use JACK for all routing, such as Qtractor.

i imagine this being implemented within the "App properties" (which maybe should be "Client Properties", since as stated above, the same application can be multiple clients in a project) dialog box as a check box that is labeled "ignore internal connections". with this checked, LADISH will a) forget all internal connections for that client (i.e. those that have that same client for both port1 and port2) b) ignore additional internal connections made for that client. if the check box is disabled, the opposite occurs: a) LADISH scans the client and remembers all internal client connections b) as before, saves additional internal connections for that client.

[http://nedko.arnaudov.name/]

I'm reducing priority because the drawback is that Ardour shows a log/warning dialog and/or there are "cannot connect already connected ports" errors in the ladishd log. I.e. there is bo broken functionality just some annoyance.