Add json-rpc api support for dropping subgraphs

[mangas]

Add json-rpc method for dropping subgraphs. Using this endpoint will remove all the subgraphs for the deployment_id and will delete the underlying data. docker/bin/drop is a helper script to use the new endpoint.

Adding some sane defaults as discussed:

 ./docker/bin/drop Qmd3vU6y6pxxXPrvVWRZMN9soNB8AFQCEnqPa9jMSZZDEG
Dropping deployment Qmd3vU6y6pxxXPrvVWRZMN9soNB8AFQCEnqPa9jMSZZDEG
{"jsonrpc":"2.0","error":{"code":1,"message":"subgraph registrar error with store: store error: multiple subgraphs exist fo
r this hash, please remove them before trying to drop"},"id":"1"}

./docker/bin/remove y
{"jsonrpc":"2.0","result":{"type":"Null"},"id":"1"}

./docker/bin/drop Qmd3vU6y6pxxXPrvVWRZMN9soNB8AFQCEnqPa9jMSZZDEG
Dropping deployment Qmd3vU6y6pxxXPrvVWRZMN9soNB8AFQCEnqPa9jMSZZDEG
{"jsonrpc":"2.0","result":{"type":"Null"},"id":"1"}%

[alex-pakalniskis]

Perhaps explore Indexer Agent-based solution to avoid graphman drop danger zone?

[mangas]

Perhaps explore Indexer Agent-based solution to avoid graphman drop danger zone?

Not sure I understand the argument here. This is a private endpoint, it's as dangerous as letting someone add subgraphs unboundedly and fill up the disks, taking down the graph-node. It is also a basic operational task that currently cannot be automated because it's not exposed in any api.

[incrypto32]

Dont this delete both the pending and current version of a subgraph that belongs to the same name as hash provided? Thought we are moving away from that behaviour?

[incrypto32]

Was the debug logs supposed to be before the self.store.drop_subgraph(id)?; ?