Application selector shows wrong team's applications after expert-driven navigation

### Current Behavior

After the expert navigated to a remote instance in a different team (one that wasn't assigned to an application), attempting to assign it to an application via the "assign device" link under the device title opened the modal with applications from the original team, not the team the device actually belongs to.

This looks like a lingering cache or incomplete navigation state, where switching teams via the expert doesn't fully update the context used by the application selector.

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Environment

- FlowFuse version:
- Node.js version:
- npm version:
- Platform/OS:
- Browser:

### Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Start by reproducing the expert-driven navigation to a device in another team, then inspect how the assign-device application selector receives its team context and whether cached state persists. Done means the modal lists applications from the device's actual team, with a regression test covering navigation between teams.

Written by the indexing model from the issue text.