[METADATA] improve subgraph related metadata

[d10r]

Example for what it currently looks like:

        "subgraphV1": {
            "cliName": "goerli",
            "name": "protocol-v1-goerli",
            "hostedEndpoint": "https://api.thegraph.com/subgraphs/name/superfluid-finance/protocol-v1-goerli"
        },
        "subgraphVesting": {
            "name": "vesting-v1-eth-goerli",
            "hostedEndpoint": "https://api.thegraph.com/subgraphs/name/superfluid-finance/vesting-v1-eth-goerli"
        },
...

Schema:

interface SubgraphData {
    readonly name: string;
    readonly cliName?: string;
    readonly hostedEndpoint?: string;
    readonly satsumaEndpoint?: string;
}

This schema was added when we had only one subgraph (protocol-v1) and only the vendor graph (hosted service).

There's several issues with the status quo:

• ignores that we now want to use canonical endpoints instead of vendor specific endpoints
• cliName is redundant if there's multiple subgraphs
• need to clarify the meaning of "name" here and how it's used

Ideally we get to an outcome which is similar to the RPCs, where there's a canonical URL template which only needs the canonical network name applied. In the case of the subgraph, the subgraph name will also be needed.
E.g. https://optimism-sepolia.subgraph.x.superfluid.dev/protocol-v1

Needs to be done in tandem with infra and products in order to avoid breakage.

Next steps:

• enumerate uses of the current subgraph related metadata (what would break if changed?)
• specify and set up a canonical subgraph endpoint schema which supports multiple subgraphs per network (while keeping existing endpoints operational)
• define new metadata schema, implement it, create a new metadata package
• define changes to be done across the stack to avoid breakage and implement them

[d10r]

this is blocked by https://github.com/superfluid-finance/garden-infra/issues/88