Now that there is a participant subscription, need to avoid `ctx:query` through its ECI

[b1conrad]

because we want ultimately to allow some of the participant picos to be on other pico engines!

So, internal queries should go through the subscription, host and all, as should events sent from list pico to child and vice versa.

Calling this both a bug (because it will be as soon as even one participant pico is on a different pico engine) and an enhancement, because fixing this will allow movement.

[b1conrad]

If there are any events that are sent, note that the subscription ruleset reacts to a wrangler:send_event_on_subs event (expecting one (or more) of these attributes: subID, Tx_role, and/or Rx_role and domain and type and attrs) which sends the specified event to all subscriptions matching.

[b1conrad]

There is nothing like that for sending a query through a subscription. So, added issue #610 to the pico-engine repo to do this. Perhaps we could try something here to test it out, and then promote it into the wrangler/subscription rulesets?

[b1conrad]

There are plenty of usages to follow through with, for events:

$ grep event:send krl/*.krl
krl/byu.hr.core.krl:    event:send({"eci":notify_eci,"eid":"child_desig_changed",
krl/byu.hr.core.krl:      event:send({"eci":event:attrs{"wellKnown_Rx"},
krl/byu.hr.oit.krl:    event:send({"eci":eci,"eid":"install-ruleset",
krl/byu.hr.oit.krl:      event:send({"eci":child_eci,"eid":"rename-child-engine-ui",
krl/byu.hr.oit.krl:      event:send({"eci":child_eci,"eid":"rename-child-wrangler",
krl/byu.hr.oit.krl:      JSON => event:send({"eci":eci,"eid":"import JSON",
krl/byu.hr.oit.krl:      TSV  => event:send({"eci":eci,"eid":"import TSV",
krl/byu.hr.oit.krl:      event:send({"eci":eci,"domain":"wrangler","type":"rulesets_need_to_cleanup"})
krl/byu.hr.oit.krl:      event:send({"eci":eci,"domain":"wrangler","type":"ready_for_deletion"})
krl/byu.hr.patch.krl:    event:send({"eci":eci,"eid":"install-ruleset",
krl/layout.krl:      event:send({
$ 

For queries:

$ grep picoQuery krl/*.krl
krl/byu.hr.core.krl:from #{wrangler:picoQuery(eci,meta:rid,"displayName")}
krl/byu.hr.relate.krl:          oRIDs = wrangler:picoQuery(eci,wranglerRID,"installedRIDs")
krl/byu.hr.relate.krl:          isParticipant => wrangler:picoQuery(eci,coreRID,"displayName")
krl/byu.hr.relate.krl:                         | wrangler:picoQuery(eci,wranglerRID,"name")
$ grep ctx:query krl/*.krl
krl/byu.hr.core.krl:      ctx:query(
krl/byu.hr.login.krl:      display_name = loggedInECI => ctx:query(loggedInECI, "byu.hr.core", "displayName") | ""
krl/byu.hr.login.krl:      wellKnown_Rx = loggedInECI => ctx:query(loggedInECI, "io.picolabs.subscription","wellKnown_Rx").get("id") | ""
krl/byu.hr.login.krl:      homeECI = loggedInECI => ctx:query(loggedInECI, "byu.hr.core", "adminECI") | ""
krl/byu.hr.login.krl:      loggedInRIDs = loggedInECI => ctx:query(loggedInECI, "io.picolabs.wrangler","installedRIDs") | []
krl/byu.hr.login.krl:      apps = loggedInRIDs >< maRID => ctx:query(loggedInECI, maRID, "apps").join(",") | ""
krl/byu.hr.oit.krl:        ctx:query(child_eci,"byu.hr.core","child_desig",{
krl/byu.hr.oit.krl:          the_eci = is_self => ctx:query(child_eci,"byu.hr.core","adminECI")
krl/byu.hr.oit.krl:          record_audio_eci = is_self => ctx:query(child_eci,"byu.hr.core","record_audio_eci") | null
krl/layout.krl:      uiECI = ctx:query(child{"eci"},engine_ui_rid,"uiECI")
$ 

[b1conrad]

Rulesets to consider:

byu.hr.login
byu.hr.oit
byu.hr.core
byu.hr.relate
byu.hr.patch

Removed layout because it has to do with child picos only, not picos on a different pico engine.