Add deploymentTimestamp and firstTimeFullySyncedTimestamp to SubgraphIndexingStatus

It would be great for subgraph developers to find out how long their subgraph took to fully sync for the first time. This could be enabled by changing the type SubgraphIndexingStatus here to the following shape:

type SubgraphIndexingStatus {
  subgraph: String!
  synced: Boolean!

  # Note that the health can be implied from fatalError and nonFatalErrors:
  # - If fatalError is non-null, then health is 'failed'.
  # - Else if nonFatalErrors is non-empty, then health is 'unhealthy'.
  # - Else health is 'healthy'.
  health: Health!

  "If the subgraph has failed, this is the error caused it"
  fatalError: SubgraphError
  "Sorted from first to last, limited to first 1000"
  nonFatalErrors: [SubgraphError!]!
  chains: [ChainIndexingStatus!]!
  entityCount: BigInt!
  node: String
  deploymentTimestamp: BigInt! # <- Added 
  firstTimeFullySyncedTimestamp: BigInt # <- Added, not required because it's empty during sync
}

Commencez par la définition de SubgraphIndexingStatus dans server/index-node/src/schema.graphql et suivez l’endroit où ses valeurs sont assemblées. Vérifiez comment obtenir les heures du déploiement et de la première synchronisation complète, puis exposez les deux champs avec le comportement requis en matière d’obligation et de nullabilité. Le travail est terminé lorsque le schéma et ses réponses incluent des horodatages exacts et que le champ de première synchronisation est vide pendant la synchronisation.