Add user to flow to StorageFlows table, to record who triggered auto snapshot

[hardillb]

part of #4413

Description

Records which user triggered the last flow deploy so it can be used in snapshot data.

Related Issue(s)

#4413

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]

Need to double check how this behaves when a snapshot is exported/imported

[codecov]

Codecov Report

Attention: Patch coverage is 86.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 78.08%. Comparing base (417df50) to head (2ea8807).
Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
forge/db/controllers/ProjectSnapshot.js	80.00%	1 Missing ⚠️
forge/db/migrations/20240920-02-add-flow-user.js	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4518      +/-   ##
==========================================
- Coverage   78.15%   78.08%   -0.07%     
==========================================
  Files         299      301       +2     
  Lines       14261    14299      +38     
  Branches     3235     3243       +8     
==========================================
+ Hits        11145    11165      +20     
- Misses       3116     3134      +18     

Flag	Coverage Δ
backend	78.08% <86.66%> (-0.07%)	⬇️

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.

[hardillb]

Needs nr-launcher pr FlowFuse/nr-launcher#287

[knolleary]

Note we now have #4526 that also contains a migration. Whichever merges first, the other one will need to rename its migration to ensure the ordering is correct.

[hardillb]

I have renamed the migration in this PR to 02 so merge the OTHER PR first

[Steve-Mcl]

Suggested change

	UserId = app.db.models.User.decodeHashid(request.headers['ff-user'])[0]
	UserId = app.db.models.User.decodeHashid(request.headers['ff-user'])?.[0] || null

[Steve-Mcl]

Suggested change

	// CHECK ME
	onDelete: 'SET NULL',
	// CHECK ME
	onUpdate: 'CASCADE'
	onDelete: 'SET NULL',
	onUpdate: 'CASCADE'

happy with cascades