Fix device log race condition between publish and disconnect

[cstns]

Description

Fix device log race condition between publish and disconnect

Related Issue(s)

missed out of #4893

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

All modified and coverable lines are covered by tests ✅

Project coverage is 78.70%. Comparing base (a7ebfe3) to head (dc693bd).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4903   +/-   ##
=======================================
  Coverage   78.70%   78.70%           
=======================================
  Files         323      323           
  Lines       15230    15230           
  Branches     3498     3498           
=======================================
  Hits        11987    11987           
  Misses       3243     3243           

Flag	Coverage Δ
backend	78.70% <ø> (ø)

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.

[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.

[knolleary]

Sorry - comment above added to the wrong PR ....