plan names of cloudflare resources and how they map to github resources

[gobengo]

Before this issue:

1. web3-storage/w3ui examples/react/console deploys to cf pages project console-web3-storage-staging
2. web3-storage/console - this repo deploys to cf pages project w3up-website-staging
3. web3-storage/www - new website repo deploys to nowhere (yet)
4. cf dns points staging.console.web3.storage to cf pages console-web3-storage-staging (the one deployed from w3ui monorepo)

Desired State:

1. web3-storage/w3ui examples/react/console deploys to nowhere (for now) or a new pages project (not console-web3-storage-staging as before)
2. web3-storage/console deploys staging to cf pages project console-web3-storage-staging (not w3up-website-staging as before)
3. web3-storage/www - deploys to cf pages project w3up-website-staging (not nowhere as before)
4. cf continues to dns point staging.console.web3.storage to cf pages project console-web3-storage-staging

### Tasks
- [x] float this in case anyone objects or wants to wait
- [x] await concerns for 24hrs+

[olizilla]

Desirable!

[alanshaw]

+1 seems correct!

[gobengo]

I did this simpler thing (https://github.com/web3-storage/console/issues/21) for now because time is tight as we can an MVP out, and I couldn't get consensus on the above. We can reopen this after that if it's still desirable to re-allocate all the cf names