e2e tests for instance and device rollback feature

[Steve-Mcl]

closes #2032

Description

• Adds e2e test for rollback feature (only testing the endpoint is present and callable, not the full mechanics which are covered by unit tests)
• Squares up the dialogs for instances/devices (instances had no kind, devices had kind:"danger") so that the tests can be equivalent and the features stay close to each other in appearance.

Related Issue(s)

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.76%. Comparing base (8718b1d) to head (a2fe3f6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4149   +/-   ##
=======================================
  Coverage   78.76%   78.76%           
=======================================
  Files         286      286           
  Lines       13053    13053           
  Branches     2910     2910           
=======================================
  Hits        10281    10281           
  Misses       2772     2772           

Flag	Coverage Δ
backend	78.76% <ø> (ø)

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.

[joepavitt]

All looks good from the code/test-side, but just wanted to check with @ppawlowski that the failing deployment is on his radar, can't see it being linked to anything introduced here

[ppawlowski]

All looks good from the code/test-side, but just wanted to check with @ppawlowski that the failing deployment is on his radar, can't see it being linked to anything introduced here

I re-run the pipeline and all looks good, can't say why the previous one failed.