Bug - Schema names incongruent between actual vs. explorer web UI

Overview

Below are 2 examples I found where the schema name of a subgraph are incongruent between the actual subgraph (i.e. what can be queried with a connection) vs. what is shown on the explorer web UI.

Impact

• It makes the subgraph look broken
• It wastes time debugging the issue

Examples

indexers

• URL: https://thegraph.com/explorer/subgraph/graphprotocol/graph-network-mainnet?query=Effective%20cuts
• Web UI: In the "Schema" section, it is noted as indexer
• Real Connection: requires indexers

This query will fail

For example, the query below would break, despite it being written to match what is shown on the explorer UI:

indexer_query = gql(
    """
    query {
        indexer {
            id,
            stakedTokens,
            delegatedStakeRatio
          }
    }
"""
)

This query will pass

indexer_query = gql(
    """
    query {
        indexers {
            id,
            stakedTokens,
            delegatedStakeRatio
          }
    }
"""
)

transactions

• URL: https://thegraph.com/explorer/subgraph/graphprotocol/graph-network-mainnet?query=Effective%20cuts
• Web UI: In the "Schema" section, it is noted as transaction
• Real Connection: requires transactions

This query will fail

query = gql(
    """
    query {
        transaction {
            id,
            blockNumber
          }
    }
"""
)

This query will pass

query = gql(
    """
    query {
        transactions {
            id,
            blockNumber
          }
    }
"""
)

Proposal

• Make sure that the schema named found in the Web UI is congruent (==) to what a user would query
• Check all other subgraphs + schemas for similar issues (I only found 2 in a few minutes of working on this, so my assumption is it's a larger issue)

Start with the Explorer web UI Schema section and compare its displayed names with the queryable schema for the graph-network-mainnet subgraph, using the indexers and transactions examples in this issue. Check the other subgraphs and schemas for the same mismatch; done means displayed names match the fields users can query and the failing example queries are no longer misleading.