Fix/queue subscribe

[connorsmith256]

Feature or Problem

This updates the host to queue subscribe to the linkdefs.* and get.* topics:

• Link def gets and puts can be handled by a single host: the host simply proxies these requests into the LATTICEDATA KV bucket, and the data watcher thread will then receive a new message and update the host's in-memory cache
• The get.* (links, claims) topics can likewise be served by a single host, since clients (should) only listen for a single reply on this topic

This also disables the handle_links trace for now, since wadm currently makes too many requests for links, generating spammy traces

This also disambiguates the handle_message function name to handle_rpc_message (handling incoming messages for actors) and handle_ctl_message (handling incoming messages for the host)

The net effect of these changes should be a reduction in traces and more clear span names

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

I started 3 hosts with trace-level logging and issued various linkdef get/put/delete commands to the hosts, confirming a single host responded to each message and that all hosts updated their internal state