global: Use reserved discriminant spaces for TypeId

[tilacog]

This rearranges TypeId variants to match graph-node's IndexForAscTypeId numbering.

[tilacog]

@evaporei I'm not sure, but I think this change would require a new pre-release version for graph-ts?
If so, then I believe we should also patch graph-cli to use this latest version, as well.

[evaporei]

@tilacog great comments 👏 ❤️

I just have a quick question, what about new Ethereum and regular types (non-attached to any chain)? Should those stick within the NEAR range?

Thanks a lot for doing this 😊

[tilacog]

I don't think we have support for blockchain agnostic types, but new Ethereum types have their own range here.

We couldn't place them next to the original Ethereum types, but there is room for them to grow over time.

[evaporei]

I don't think we have support for blockchain agnostic types

I mean types like String, ArrayBuffer, etc.

[tilacog]

Hm, I see.

Since they were placed next to Ethereum types, originally, I think we can continue placing them as so.
We still have ~500 slots reserved for that. If that is not enough, we can reserve more slots at the end.

Do you think that would work?

[tilacog]

@evaporei It seems CI is not running for this, so I can't merge it.
I can't see any associated checks for this PR, though.