Import flows on instance creation

[cstns]

Description

BE:

• added flows as an optional parameter on instance creation
• added gate to prevent simultaneous blueprint/flow deployment
• when flows are present on the request, a new StorageFlow will be created to deploy them to the newly created instance

UI:

• renamed the multi-step-form blueprint step to flows to allow both blueprint and flows import
• altered the multistep form styling for a better scrolling experience
• force re-render the FlowViewer when flows change in order to support re-renderings on flows change
• preserved the blueprint step name when deploying flows and disabled the section selector in that scenario
• hides blueprint section and section selector when blueprints are not present
• flows can be uploaded via a file or pasted in a textarea with immediate rendering

Related Issue(s)

closes #5751

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.
  • Add changelog entry for importing flows during instance creation website#4004

Labels

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

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.82%. Comparing base (17ce7dd) to head (735f894).
⚠️ Report is 52 commits behind head on main.

Files with missing lines	Patch %	Lines
forge/db/controllers/Project.js	50.00%	4 Missing ⚠️
forge/routes/api/project.js	50.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6137   +/-   ##
=======================================
  Coverage   76.82%   76.82%           
=======================================
  Files         381      381           
  Lines       19306    19330   +24     
  Branches     4647     4653    +6     
=======================================
+ Hits        14831    14850   +19     
- Misses       4475     4480    +5     

Flag	Coverage Δ
backend	76.82% <50.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hardillb]

Initial things:

1. the warning is too big env on my 4k screen

The box to paste the flow into is hidden until I mouse over it.

[hardillb]

Functionally works as expected

Not a fan of the clear button on the side at full hight like that

Having the "blue warnings" at the bottom is better, still takes up more space than I'd like at some screen sizes.

There is still some odd layout at some window sizes, but I can probably let that go

Screencast.From.2025-10-17.11-33-51.mp4

Will read the code to see if I spot anything else then will approve this PR to merge to the other one and we can decided if there are any other tweaks needed

[cstns]

The button is definitely not supposed to be displayed like that, taking a look

[hardillb]

Pretty happy with this via testing

Just the note about the POST schema

[hardillb]

@cstns is this "done"? I'll trigger re-run of the UI tests and have one last look

[cstns]

it's done, yes, but the e2e tests are only failing on GH actions and not locally. The artefacts are not conclusive and don't even know how to approach this. And there's also the docker/aws outage

[hardillb]

Approved, pending a clean UI test run