Split & shift the "Protect Instance" setting for an Instance

### Description

We have 3 states that the NR Editor can be configured to run in:

- Open: Access for view/edit as "normal"
- Protected: View-only mode whereby the Node-RED Editor allows viewers of the flows, but no "Deploy" actions.
- Disabled: The Editor cannot be accessed at all, by anybody

The complexity here is that the "Disabled" state still allows writing of flows via a Pipeline _by anybody_. The "Protected" mode only enables Team Owners to push Pipeline stages to this instance.

A point of friction here too is that the setting to set "Protected" mode is in a different tab to that of the "Disabled" option. We should unify these options under the "Editor" tab,

### Current State

#### Editor Settings

#### Protect Mode

### Proposal

A new "Editor Access" option within the "Editor" tab. These then provides a dropdown for three options:

- Available
- View-Only
- Disabled

A new "Read/Write Permissions" option within the Editor tab, which is available when "Editor Access" is "View-Only" that provides the following options:

- Disabled - No changes can be pushed to this Instance at all
- Pipelines Only (Team Owner) - Changes can be pushed via Pipelines if you are a Team Owner
- Pipelines Only (Team Owners + Members) - Changes can be pushed via Pipelines if you are a Team Owner or Team Member

#### Availability in Tiers

It's worth noting here that the current "Protected Mode" is an Enterprise-only feature, so the current "Protected" option would not show at other tiers. I'm not sure (at the time of writing) how tied together the view-only and team-only write access for Pipelines is, so may need to modify this slightly when implementing

### Epic/Story

_No response_

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

I have provided an initial effort estimate