[7550] Fix rbac specs failing in CI

[n-lark]

Description

These specs flaked because the Remote Instances page fires two concurrent /teams/{id}/devices requests on load, the full list and a nameless statusOnly poll, and the before() hook's intercept matched both.

It intermittently captured the response without device names and every devices.find(i => i.name === …) returned undefined. The fix narrows the intercept to the full request (which always carries page=1, unlike the statusOnly poll), making the captured data match up.

Related Issue(s)

Resolves #7550

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.

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 76.95%. Comparing base (525a175) to head (495aed4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7555   +/-   ##
=======================================
  Coverage   76.95%   76.95%           
=======================================
  Files         410      410           
  Lines       21002    21002           
  Branches     5117     5117           
=======================================
  Hits        16162    16162           
  Misses       4840     4840           

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

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

☔ View full report in Codecov by Harness.
📢 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.

[cstns]

Should we maybe dig into the root cause of why there are two concurrent /teams/{id}/devices calls happening? That feels like it might be the actual thing that's out of place here, rather than the e2e tests themselves

[n-lark]

Hey @cstns so the two calls are:

1. loadDevices() → /devices?limit=25&page=1 — the paginated table data (25 full device objects → this.devices).
2. pollForDeviceStatuses() → /devices?statusOnly=true — all devices, status-only fields → this.allDeviceStatuses.

If we wanted to split the statuses into their own endpoint we could but I think that is a larger refactor than we should handle for this ticket.

When I pick back up Replace HTTP polling of instance / device status with MQTT-over-WS
#7324 I could take a look at changing this in parallel if we think that is worth our time.

[cstns]

#7324 I could take a look at changing this in parallel if we think that is worth our time.

needs a look at for sure but well see if we actually need to do something about it