Log client app version in websocket heartbeats to be displayed for admins

[RyanMG]

Ticket #3947

Server update here

Hoist P/R Checklist

• Caught up with develop branch as of last change.
• Added CHANGELOG entry, or determined not required.
• Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
• Updated doc comments / prop-types, or determined not required.
• Reviewed and tested on Mobile, or determined not required.
• Created Toolbox branch / PR, or determined not required.

[amcclain]

Great, thanks for jumping on this! Just had a chance to update the ticket with a proper description.

Goal is to get this version info into the Hoist admin console grid. We'll need to look at hoist-core to see how these messages are handled and thread that through into the HoistWebSocketChannel object, which is what is holding the state reported by that grid.

[RyanMG]

120 is holding "7.0 SNAPSHOT" with no issue, but unsure how much we expect this value could grow.

[RyanMG]

I initially made data an object and sent clientAppVersion as a property in said object.

I am unsure though how clients may be using this service. If they are extending and overriding data in sendMessage we would lose this value. However, there is also nothing stopping them from overriding heartbeatOrReconnect either.
Open to suggestions or notes to help better understand real world use cases.