Add `data plane` selection into the create and edit flow

[ ] We will try to keep this being a super small MVP
[ ] This is not immediately visible to all users. Want only certain users to see this by providing them a URL param.
[ ] User needs needs to provide at the same time as name.
[ ] User can select a data plane while creating an entity
- [ ] User cannot change during edit
[ ] data_plane_name as what the user sees for the data plane
[ ] If there are private data planes then those should be used first
[ ] Stretch Goal - adding a default data plane that can be set on tenants
[ ] Display should be grouped by private/public and look similar to collection key selection grouping always/sometimes exist

Selecting data plane

Up there with naming the task. This could be up along with the entity name
During edit this cannot be changed
There is a default data plane on publications / discovers
Disable this for the edit workflow
- Once a live spec is created it will live in that data plane forever
Names still need to be unique (not just within a data plane)

Tables

Data planes table is there today
The data plane table is queryable with RLS… users can only read those that they can use
List by the data_plane_name
Needed even for discovers
data_plane_fqdn - a fully qualified domain name

Rendering Data Planes

estuary / ui