Device UX Review

### Description

Having just done a [UX Review on Devices](https://www.figma.com/file/JlbuwrGYgxYOV3DKlLck9J/User-Journeys---Devices?type=whiteboard&node-id=0%3A1&t=KCBhnqf2CBCl5yk3-1) I've flagged multiple areas of frustration and ideas for improvement that I'll be documenting here:

### Setup Phase - Adding a Device

```[tasklist]
- [ ] https://github.com/flowforge/flowforge/issues/2428
- [ ] https://github.com/flowforge/flowforge/issues/2456
- [ ] https://github.com/flowforge/flowforge/issues/723
- [ ] https://github.com/FlowFuse/flowfuse/issues/3295
```

### Setup Phase - Download YML

```[tasklist]
- [ ] https://github.com/flowforge/flowforge/issues/2429
- [ ] https://github.com/flowforge/flowforge/issues/2430
- [ ] https://github.com/FlowFuse/flowfuse/issues/3256
```

### Setup Phase - Binding Device to Instance

This entire step feels very unintuitive. #2334 seeks to move the Devices to nest below Applications, rather than Instances, which would have some level of impact here as currently, to deploy a set of flows to a Device, you need to go via a Snapshot on an Instance first.


```[tasklist]
- [ ] https://github.com/flowforge/flowforge/issues/2431
- [ ] https://github.com/flowforge/flowforge/issues/2432
```

### Action Phase - Setting Target Snapshot


```[tasklist]
- [ ] No "Target Snapshot" define on "Instance > Snapshot" page
- [ ] Creating a snapshot, feels a little empty, no context as to content of flows/snapshot.
- [ ] Not obvious you can click "Application" and "Instance" in the Devices table
```

### Action Phase - Developing Flows on Device

```[tasklist]
- [ ] https://github.com/flowforge/flowforge/issues/2486
- [ ] Not clear why Editor is disabled for Devices
- [x] "Enable" button to toggle Editor Access should be a toggle switch
```

Start with the linked Figma UX review and the task-list issues for device setup, YAML download, device binding, snapshots, and editor access. The review is complete when the listed UX findings have been split into actionable issues or otherwise resolved, with each requested interaction change clearly defined.

Written by the indexing model from the issue text.