restricting the number of spaces per providers

[heyjay44]

Timing: start work the week of April 10th

Frontend approach: remove option to create a space in the CLI and console
Alternatively, this can be updated in the backend.

[gobengo]

iirc the goal here is to either:

1. enforce a limit of one provider/add (which results in a 'provision') per space
2. enforce a limit of one 'provider' across all provisions per space.
   • i.e. it would be ok for a space to have two provider/add invocations result in provisions as long as the two provisions had identical provider (i.e. they were both 'did:web:nft.storage').

For now I prefer number 1. afaik there is no current need for multiple provisions on a space, so it might just be simpler to enforce a 1:1 mapping space<->provision<->provider in the immediate term. (especially considering the following context). Do you have any concerns with that @Gozala ?

The goal as I recall would be to:

• make it unlikely that any given space 'is registered with different storage providers'
• (no other critical use case, so doing something simple is fine)

[gobengo]

I just looked and what I advocated for above is already implemented via #595

@heyjay44 I think that means no more work is required for this backend-wise.