feat: Add support for FlowFuse Expert Broker

[ppawlowski]

Description

This pull request adds support for FlowFuse Exper Broker configuraiton

Related Issue(s)

#889

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

[hardillb]

For this feature to work, team broker must also be enabled (as it sets up a bridge from the EMQX broker to the central broker). So we will need to a gate that is forge.expert.broker is set then forge.broker.teamBroker.enabled must also be true.

This is the stuff I was looking at on Thursday last week e.g.

_helper.tpl

...
{{- define "forge.validateExpertInsights" -}}
{{- if and ((.Values.forge.expert).insights).enabled ( not .Values.forge.broker.teamBroker.enabled ) -}}
    {{ fail "forge.broker.teamBroker.enabled=true is required for forge.expert.insights.enabled=true "}}
{{- end -}}
{{- end -}}

{{- define "forge.emqxAPIHost" -}}
{{- if ((.Values.forge.broker.teamBroker).api).url -}}
  {{ .Values.forge.broker.teamBroker.api.url }}
{{- else -}}
  "http://emqx-dashboard.{{- .Release.Namespace -}}:18083"
{{- end -}}

We can also work out the default emqx api hostname