Document & codify release and deployment process

[Atmosfearful]

We have a peculiar release process for reasons discussed here - KlimaDAO/klimadao#1652

Consumers (carbonmark-api and FE) prefer to consume subgraphs via ID instead of names, so we can be deliberate about when we consume breaking changes.
However, until we migrate to the decentralized net, pushing to an existing deployment will break old IDs. This puts us at risk of breaking production deployments.

Please write a guide for new developers who wish to deploy a Subgraph enhancement:

• how do you deploy, what is needed to deploy (permissions, tooling, etc.)
• what are our conventions around creating a new named deployment
• why is it done this way (to avoid breaking old releases, etc. etc.)

[0xemc]

@cujowolf If you could follow the format set here:

https://github.com/KlimaDAO/klimadao/wiki

That'd be helpful if we one day decide to merge these repos or create a unified docs