Add Ui-Control modifications.

[kd9lsv]

Description

Adds ui-control to migration list.

Related Issue(s)

Resolves #30

Checklist

• [Y] I have read the contribution guidelines
• [Y] Suitable unit/system level tests have been added and they pass
• [Y] Documentation has been updated
  • [N/A] Upgrade instructions
  • [N/A] Configuration details
  • [N/A ] Concepts
• [ N/A] Changes flowforge.yml?
  • [N/A ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • [ N/A] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• [N/A] Includes a DB migration? -> add the area:migration label

[joepavitt]

Whilst the node migration for ui-control here is simple, the complexity actually comes with the preceding nodes in the flow. Given that we have changed the required data structure being passed into a ui-control node, flows will not migrate smoothly and offer the same functionality, even though with this change the new ui-control node will be visible and present.

The only option I could consider here is that we include both a ui-control node from D2.0, and a function or change node that precedes it which does the conversion between the D1.0 and D2.0 object structures.