Define postresql schema update strategy

[juli4n]

In #731 we added a PostgreSQL based backend to replace ValKey. We need to define how Substrate will keep track of DDL commands to evolve the SQL schema, and the machinery to run / apply the schema changes during upgrades in a reliable way.

[EItanya]

Jeremy Alvis (@iplay88keys) assigning you.

It won't let me officially do it...

[iplay88keys]

Edit: The proposal doc is now at: https://docs.google.com/document/d/13ixDKRoAIFXeLxS-_1nikNcAy76ca8m0eVgobfib93E/edit?usp=sharing (need to be part of the ate-dev@googlegroups.com google group to access)

[maxsmythe]

I'm in ate-dev, but no access?

[iplay88keys]

I'm in ate-dev, but no access?

Max Smythe (@maxsmythe) I'm looking into this. It seems like an org-level sharing policy that I don't have visibility into. I'm working with my IT team to resolve it. Can you request access in the meantime?

[iplay88keys]

I have a PR up for this here: #1196

[iplay88keys]

Julian Gutierrez Oschmann (@juli4n) Max Smythe (@maxsmythe) In order to resolve the share permissions, I had to move the doc. The new link is here.