Change blockchain IDs types from string to number

[ipapandinas]

Description of what the problem is

Currently all blockchain IDs are recorded as string inside the database.
This design was driven by the forked concepts from the subquery project.
However this leads to an unwanted side effet when sorting with orderBy.

For example if you want to sort NFT by ascendant nftId you will face this bad behaviour:

# Submitted query
{
  nftEntities(orderBy: NFT_ID_ASC) {
    nodes {
      nftId
    }
  }
}

// Returned data
{
  "data": {
    "nftEntities": {
      "nodes": [
        {
          "nftId": "0"
        },
        {
          "nftId": "1"
        },
        {
          "nftId": "10"
        },
        {
          "nftId": "100"
        },
        {
          "nftId": "1000"
        },
        {
          "nftId": "10000"
        },
        {
          "nftId": "10001"
        },
        {
          "nftId": "10002"
        }
      ]
    }
  }
}

Why there is no a simple solution?

Since MAX_SAFE_INTEGER= 9007199254740991, common javascript numbers could be used instead strings.
However this change inside the GraphQL shema conducts to an inconstancy on nested entities (e.g.collection: CollectionEntity inside NftEntity).

In fact, database item ID collectionId conflicts with collectionId item from blockchain data.
We end up with inconsistencies of this kind depending on the entity used 👇

Submitted query on nftEntities

{
  nftEntities(orderBy: NFT_ID_ASC) {
    nodes {
      nftId
      collectionId
    }
  }
}

// Returned data
{
  "data": {
    "nftEntities": {
      "nodes": [
        {
          "nftId": 0
          "collectionId": null
        },
        {
          "nftId": 1
          "collectionId": "0"
        },
        {
          "nftId": 2
          "collectionId": "7"
        },
      ]
    }
  }
}

Submitted query on collectionEntities

{
  collectionEntities(orderBy: COLLECTION_ID_ASC) {
    nodes {
      collectionId
      nfts
    }
  }
}

// Returned data
{
  "data": {
    "collectionEntities": {
      "nodes": [
        {
          "collectionId": 0
          "nfts": [1]
        },
        {
          "collectionId": 1
          "nfts": []
        },
        {
          "collectionId": 2
          "nfts": [13, 14, 15]
        },
      ]
    }
  }
}

As you can collectionId is an string in nftEntities but a number in collectionEntities. We want to avoid this inconsistency.