Standardise the property label instead title

[gayanSandamal]

Description

@joepavitt @Steve-Mcl
As this related issue is only mentioned about the docs update but as per my understanding it should update all the areas of gauge node related with title but this will lead to a problem with the existing gauges that currently use title property in NR flows.

Therefore the dashboard users have to update their flows otherwise I should limit this PR just for a one line docs update

Related Issue(s)

#1284

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

[joepavitt]

The only request was to support ui_update.label in the dynamic properties functionality, and for thag to then, under the covers, update the title property.

The title field doesn't need to change, this should require no changes from the user.

[joepavitt]

The other option here is that we keep these changes, do move forward with label, but support injection of config.label if a config.title is present in the js file when the node is registered. This will prevent the need for users to manually update.

@Steve-Mcl can talk you through that process if required.

[Steve-Mcl]

The title field doesn't need to change, this should require no changes from the user.

This is the preferred direction IMO. It will be seamless to the user. We will continue to use title in the flows and continue to support ui_update.title (but depreciate it) and support ui_update.label going forwards. Under the hood, ui_update.title and ui_update.label should be stored in the datastore as the same prop (I propose that prop is label). I also propose we do not mention title in the docs (even though it will continue to work as before)

Gayan and I have discussed this. If I get time today i will make the changes to this branch/PR otherwise, Gayan is to pick it up in the morning.

@gayanSandamal let me know is anything needs further clarification please. Ta.

[gayanSandamal]

The title field doesn't need to change, this should require no changes from the user.

This is the preferred direction IMO. It will be seamless to the user. We will continue to use title in the flows and continue to support ui_update.title (but depreciate it) and support ui_update.label going forwards. Under the hood, ui_update.title and ui_update.label should be stored in the datastore as the same prop (I propose that prop is label). I also propose we do not mention title in the docs (even though it will continue to work as before)

Gayan and I have discussed this. If I get time today i will make the changes to this branch/PR otherwise, Gayan is to pick it up in the morning.

@gayanSandamal let me know is anything needs further clarification please. Ta.

Thank you so much Steve. I will talk to you if I need further clarifications on this

[Steve-Mcl]

Approved. Merged only after tests pass

[Steve-Mcl]

looks good - only the usual ✖ widgets/control.spec.js fail