document steps to publish a subgraph to the network that is not supported by studio

[matthewdarwin]

It is possible to publish subgraphs on the network that are not supported in studio. This process should be well documented, and aligned with the upcoming changes to the CLI.

Perhaps CLI and docs changes should be made together? @alex-pakalniskis

For this flow:

A developer should

1. write substreams module, test it, make sure it works (if a substreams powered subgraph)
2. write subgraph with triggers that uses that substreams package (or just a normal subgraph)
3. test it locally with local instance of graph node
4. deploy on the decentralized network with the cli tool "graph publish" and ask indexers on the Graph server to pick it up (which channel in discord should they ask?)
5. start querying it

[p-diogo]

@matthewdarwin , we have it documented, but we can do much better. I was personally waiting for a few things to be done first. My sense of dependencies:

1. Get the new GitHub-based chain registry going (WiP)
2. Update the CLI subgraph publish experience:
   a) pull network names from the registry and provide
   b) provide an option to add a new network name if non-existent (link to a contributing.md on the chain registry repo or something like that)

Once we have this, we should be able to update the docs, and onboarding chains may become a lot easier once we have this + DIPS/Indexing Fees (I will not get into the details of it to keep this thread clean).

[matthewdarwin]

CC @YaroShkvorets on cli requirements