Support disabling instance launcher "auto safe mode"

[Steve-Mcl]

closes #4920

Description

Adds setting for launcher: disableAutoSafeMode
Updates UI to permit setting of disableAutoSafeMode
Updates unit test to ensure value is persisted

Related Issue(s)

owner: #4920
parent: #4552

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.65%. Comparing base (bdf5dae) to head (3b3b6a8).
Report is 59 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4922      +/-   ##
==========================================
+ Coverage   78.63%   78.65%   +0.02%     
==========================================
  Files         324      324              
  Lines       15265    15280      +15     
  Branches     3507     3513       +6     
==========================================
+ Hits        12003    12018      +15     
  Misses       3262     3262              

Flag	Coverage Δ
backend	78.65% <100.00%> (+0.02%)	⬆️

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]

Just need a nr-launcher version gate on showing the settings so the user knows to upgrade the stack to enable the feature

[hardillb]

Also when I toggle the checkbox the "save settings" button is not being enabled (or changing the health check timeout)

The data section doesn't appear to have been updated to include the new value so it's not getting tracked.

[Steve-Mcl]

Also when I toggle the checkbox the "save settings" button is not being enabled (or changing the health check timeout)

The data section doesn't appear to have been updated to include the new value so it's not getting tracked.

That was working for me, but good spot on missing data entries (now added)

[hardillb]

Toggling the checkbox is still now marking the save settings button as active

[Steve-Mcl]

Toggling the checkbox is still now marking the save settings button as active

What browser?

Works for me in Chrome.

[hardillb]

@Steve-Mcl take hte 5000 out of the box at the top, the default is empty

[Steve-Mcl]

@Steve-Mcl take hte 5000 out of the box at the top, the default is empty

Ah, ok. This was existing behaviour but now there is more than one setting on the form, it matters!

I'll modify the form to show the default health value so the validation works.

[Steve-Mcl]

ok, fingers crossed, 3rd time is sure to be the charm.

I've added the v-else message that some settings are not available until stack is upgraded.

I set the local health value input to the launchers default (even if not set in the DB settings) - this way, there are no validation errors and the Auto Safe Mode toggle can be operated/changed/saved.

Lastly I made sure settings are only passed/updated if changed.

[hardillb]

But not merging as the updated stacks won't be available until release.

We should merge this on release day along with #4900