[Tracking] Feature parity with legacy core network subgraph

[chriswessels]

Feature parity with the existing core network subgraph to the extent that core workloads (e.g. indexer-agent, gateway, etc) require.

• [x] 1

  type Allocation {
  ageInEpochs: Int!
  signalledTokens: BigInt!
  status: AllocationStatus
  createdAtEpoch: number
  createdAtBlockHash: string
  createdAtBlockNumber: number
  closedAtEpoch: number
  closedAtEpochStartBlockHash: string 
  previousEpochStartBlockHash: string
  closedAtBlockHash: string
  poi: string
  }

• [x] 2

  type GraphNetworks {
  isPaused: Bool!
  }

• [x] 3

type SubgraphVersion {
  version: Int!
  createdAt: Int!
  deployment: String!
}

• [x] 4

  type Subgraph {
  id: String!
  versionCount: Int!
  versions: [SubgraphVersion]!
  }

• [x] 5

  type SubgraphDeployment {
  ipfsHash: String!
  deniedAt: Int!
  indexerAllocations: [Allocation]!
  }

• [x] 6

  
  type Epoch {
  id: number
  startBlock: number
  startBlockHash: string | undefined
  endBlock: number
  signalledTokens: number
  stakeDeposited: number
  queryFeeRebates: number
  totalRewards: number
  totalIndexerRewards: number
  totalDelegatorRewards: number
  }

Related spike: #45 

[juanmardefago]

L2 transfer tools support:

• Agent will require at least startedTransferToL2At (timestamp) and transferredToL2 (boolean) for SubgraphDeployment (small caveat, SubgraphDeployment doesn't have startedTransferToL2At in the network subgraph, so I already pinged Tiago about this, waiting on his response)
• Unsure about Gateway requirements, as I don't have the code at hand. Most likely going to be using a combination of the transferredToL2-like booleans and auxiliary fields (timestamp, block number, transaction hash, etc)
• L2 transfer tools also cause some side effects due to how they manage GRT balance changes due to transfers into and out of L1-L2. For the L2 side, the transfer tools trigger the normal code paths for inflows, so probably not a lot to do there, but for the L1 side, not a single one of the events for withdrawals are triggered, so they have to be handled manually within the L2 transfer tool events to get the correct values that are left over in L1. (i.e. to know the balances left over in L1 for Indexers, Delegators, Curators and Subgraphs)

[juanmardefago]

Fields we need to have regarding L2 transfer tools:

• id
• idOnL1
• idOnL2
• startedTransferToL2
• startedTransferToL2At
• startedTransferToL2AtBlockNumber
• startedTransferToL2AtTx
• transferredToL2
• transferredToL2At
• transferredToL2AtBlockNumber
• transferredToL2AtTx