Add team broker mqtt agent support

[hardillb]

part of FlowFuse/flowfuse#5951

Description

Adds Team Broker support to MQTT Schema agent

Related Issue(s)

FlowFuse/flowfuse#5951

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
• Link to Changelog Entry PR, or note why one is not needed.

Labels

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

[knolleary]

Whilst this driver is mostly for local testing as this is a license feature which localfs isn't typically used, I do think there are some lifecycle handling challenges with the agent - which could extend back to the existing 3rd party agent support as well.

My concern is around 'reattaching' to the process after a forge app restart - and whether you can end up with multiple agents running.

Am going to approve to help move things forward, but I do think this needs looking at.

[hardillb]

I have a fix that ensures the agent shuts down with the forge app and is restarted (and does the same for the Nod-RED instances).

I just need to work out if the restart should be with the full 24hrs or reduced by elapsed time.