L2 transfer tools support

Added support for L2 transfer tools:

• Adds fields to denote when a Subgraph, Indexer, DelegatedStake, NameSignal and SubgraphDeployment has been transferred to L2 (albeit the last one is just to make indexer-agent integration easier)
  • transferredToL2: Whether the L2 transfer has happened
  • transferredToL2At: Timestamp for the L2 transfer
  • transferredToL2AtBlockNumber: Block number for the L2 transfer
  • transferredToL2AtTx: Transaction hash of the L2 transfer
  • Additionally, Subgraph transfers have a startedTransferredToL2 (and all auxiliary fields), since the Subgraph transfer isn't a single step procedure.
• Adds fields to denote the transfer of GRT through the different transfer tools for the aforementioned entities

Added SbS/SpS detection and minor fixes

v0.19.1

fix(bridge): dont use hardcoded chainid when calculating retryables o…

Arbitrum Hotfix and GIP-0037 issuance support

• Fixes ENS issues in Arbitrum
• Add support for post GIP-0037 issuance
• Added tracking of totalGRTMintedFromL2

Fix off-by-one error on Epoch entity for new environments

v0.18.2

fix: off-by-one error on new environments

Add automation for non-ipfs deployments

v0.18.1

fix: naming on new workflows

Improve bridge deposit/withdrawal support

More details in the original PR #205

Bump contracts version

v0.17.1

chore: update yarn.lock

Added L1 block numbers for L2 deployments

This change is required due to the L2 contracts relying on L1 block numbers for Epoch calculations.
In order to properly predict Epoch creation, we need to also have the L1 block number available when doing the calculations, so that the settings from the contracts (epochLength) make sense in the subgraph.

Making EthereumDIDRegistry address configurable

v0.16.1

fix: use default ethDIDRegistry for arbitrum if we can't find it

L2 aware subgraph

This release includes some basic L2 aware features, like total GRT deposited/withdrawn from L2 (although only one is visible at a time, given that deposits are visible from a deployment on L1, while withdrawn is only visible from a deployment on L2).

It also includes a refactor to the github workflows due to multiple changes (rinkeby deprecated in favour of goerli, L1/L2 deployments per environment, etc).