Don't assume App TRK if service has no value at all for 'is-sys-trk' property

Connected service properties need to be propagated just as their statuses are

Merge commit

Bug 11067: fix some issues with the PNP launch wizard 1) If Sys TRK is detected, and you select to install a package, a Sys TRK launch is created 2) Error message was confusing when Carbide chose to install a package but SIS configuration was not complete. 3) In an internal layout, assume Sys TRK is more likely than App TRK if we cannot tell from the connection.