`schema.graphql` audit

[WooSungD]

Objectives of this task are:

• Identify essential entities
• Identify any unnecessary entities (with related handlers/configs) or unused entities (by analytics / FE)
• Identify additional desired entities (future scope)
• Document final list of entities

Having a refined set of entities in the schema.graphql will result in only the absolutely necessary entities being created / contracts indexed and events handled.

As an example, the following entities (once confirmed events are being indexed correctly) can be removed:

type DynamicFeeSwapModule_CustomFeeSet {
  id: ID!
  chainId: Int!
  pool: String!
  fee: BigInt! @config(precision: 76)
  timestamp: Timestamp!
  transactionHash: String!
  blockNumber: Int!
  logIndex: Int!
}

type DynamicFeeSwapModule_SecondsAgoSet {
  id: ID!
  chainId: Int!
  secondsAgo: BigInt! @config(precision: 76)
  timestamp: Timestamp!
  transactionHash: String!
  blockNumber: Int!
  logIndex: Int!
}

type DynamicFeeSwapModule_ScalingFactorSet {
  id: ID!
  chainId: Int!
  pool: String!
  scalingFactor: BigInt! @config(precision: 76)
  timestamp: Timestamp!
  transactionHash: String!
  blockNumber: Int!
  logIndex: Int!
}

type DynamicFeeSwapModule_FeeCapSet {
  id: ID!
  chainId: Int!
  pool: String!
  feeCap: BigInt! @config(precision: 76)
  timestamp: Timestamp!
  transactionHash: String!
  blockNumber: Int!
  logIndex: Int!
}

in favour of keeping

type Dynamic_Fee_Swap_Module {
  id: ID!
  pool: String!
  baseFee: BigInt! @config(precision: 76)
  feeCap: BigInt! @config(precision: 76)
  scalingFactor: BigInt! @config(precision: 76)
  currentFee: BigInt! @config(precision: 76)
  timestamp: Timestamp!
  chainId: Int!
  blockNumber: Int!
}