feat: Display workerName and processInfoId in the console status bar

[vbabich]

Get optional workerName and processInfoId along with the login options response from the DHE host, display in the console status bar.

[codecov]

Codecov Report

Merging #1173 (5307025) into main (5142a4d) will increase coverage by 0.05%.
The diff coverage is 62.74%.

❗ Current head 5307025 differs from pull request most recent head 43a3630. Consider uploading reports for the commit 43a3630 to get more accurate results

@@            Coverage Diff             @@
##             main    #1173      +/-   ##
==========================================
+ Coverage   44.21%   44.26%   +0.05%     
==========================================
  Files         449      450       +1     
  Lines       33449    33480      +31     
  Branches     8409     8420      +11     
==========================================
+ Hits        14789    14820      +31     
  Misses      18610    18610              
  Partials       50       50              

Flag	Coverage Δ
unit	44.26% <62.74%> (+0.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/code-studio/src/main/AppInit.tsx	0.00% <0.00%> (ø)
packages/code-studio/src/main/SessionUtils.ts	0.00% <0.00%> (ø)
...ckages/dashboard-core-plugins/src/redux/actions.ts	27.77% <ø> (ø)
...dashboard-core-plugins/src/panels/ConsolePanel.tsx	46.52% <66.66%> (+0.48%)	⬆️
packages/jsapi-utils/src/MessageUtils.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[mofojed]

Yea I think you're right, if we just look at the id, we don't need to bother looking at response, and then the signature can just be requestParentResponse(request, timeout)...

Thinking about this a bit further, there's basically three types of messages we can send:

• request: Something we expect a response for
• response: Responding to a request
• notify: Sending a message we do not expect a response for
  Perhaps we should do that instead... or even just have those as the three different message types... io.deephaven.message.Request, io.deephaven.message.Response, and io.deephaven.message.Notify, and then the payload itself has the details...

I'm just trying to think how we'll want to extend this later for multi-window messaging/embedding in iframes. Let's discuss later today.

[vbabich]

Resolved conflict in ConsolePanel.test.tsx and rebased.