feat: Add possibility to customise service type created for project deployment

[ppawlowski]

Description

This pull requests adds the forge.projectServiceType value which allows to define a service type created for NodeRED deployments. Currently, only ClusterIP (default value from the Kubernetes driver) and NodePort service types are supported.

Related Issue(s)

closes FlowFuse/flowfuse#4041

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

[hardillb]

Docs suggestion again.

Also this will need to be done for the mosquitto broker service as well (and look to see if needs applying to emqx)

[ppawlowski]

Also this will need to be done for the mosquitto broker service as well (and look to see if needs applying to emqx)

Ok, so maybe I misunderstood the issue - do we want to add a possibility to create all services (core app, brokers, file-service) as NoidePort, instead of ClusterIP?

[hardillb]

@ppawlowski any that are pointed to by an ingress route

[ppawlowski]

@ppawlowski any that are pointed to by an ingress route

Handled in separate PR: #547