ES: Fix memory leak and logs not flushing

graph: Updates notes on web3 and ethabi depedencies

core, graph: Add the deployment id to internal log messages

The id makes it easier to distinguish between log messages coming from
different copies of the same subgraph

note about supported ipfs version

store: Change the primary key on subgraph_deployment

Make 'id' the primary key on subgraph_deployment so that entries there are
identified with the same id as entries in deployment_schemas

graphql: Add `subgraphError` argument only when feature is present

We saw an issue in a graphql client that is avoided by doing this.
and it is generally more correct to only include it if the subgraph opts in.
This requires storing the `features` field in the metadata, which we should be doing anyways.