Ensure device logs always shown

[hardillb]

fixes #4832

Description

This triggers a publish of the logs history every time the tab is opened. It does this by explicitly telling the device agent it has disconnected when navigating away from the tab.

Related Issue(s)

#4832

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Includes a DB migration? -> add the area:migration label

[codecov]

Codecov Report

Attention: Patch coverage is 10.00000% with 9 lines in your changes missing coverage. Please review.

Project coverage is 78.70%. Comparing base (b545283) to head (d5e59ad).
Report is 15 commits behind head on main.

Files with missing lines	Patch %	Lines
forge/comms/commsClient.js	0.00%	5 Missing ⚠️
forge/comms/devices.js	20.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4893      +/-   ##
==========================================
- Coverage   78.74%   78.70%   -0.04%     
==========================================
  Files         323      323              
  Lines       15221    15230       +9     
  Branches     3496     3498       +2     
==========================================
+ Hits        11986    11987       +1     
- Misses       3235     3243       +8     

Flag	Coverage Δ
backend	78.70% <10.00%> (-0.04%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cstns]

running fine locally

[knolleary]

This PR has broken the logs when you have more than one user access them. By triggering an unsubscribe when leaving the page, it stops log delivery to other users viewing the device. When you open the device log view it triggers the buffer to be resent and is received by all users viewing the log.

This needs to be reverted.

[hardillb]

I believe this was already the case with the old way as well.

Actually no, but it relied on a race between the keep alive and the log shutdown

[cstns]

could we namespace the events to target a single user?

[hardillb]

The quick revert is to remove the publish from the unmounted while we look again