Pipeline device stage cannot be edited and looks like it is deploying

### Current Behavior

Upon adding a device to a pipeline, i see this:


The issues I see here are:
1. It is not actually deploying to a 2nd stage (it has just been added) - it just has a newer target snapshot than active snapshot.
* _While working on the device (in dev mode), I have taken snapshots along the way. I DID set the check "set as target" because if I switch out of dev mode I want the latest snapshot to be the running snapshot_
2. I cannot edit/remove this stage

### Expected Behavior

The way we determine a pipeline is deploying is not perfect. As far as i remember, we use the snapshot target being different to the actual as the flag for "deploying". That does not mean the first stage of a pipeline is actually being pushed.

We likely need to look at a better means of determining a pipeline has been operated.

### Steps To Reproduce

1. Take a snapshot of a device and set as target
1. this is because you want the device to be running latest snapshot in the event of switching it out of dev mode
2. create a new pipeline
3. set the 1st stage as the device

### Environment

- FlowFuse version: FFC (2.13)
- Node.js version:
- npm version:
- Platform/OS: win 11
- Browser: Chrome latest

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

I have provided an initial effort estimate