Chained metadata, v1

[roman-khimov]

Is your epic related to a problem? Please describe.

I'm always frustrated when we don't have any real solution for the metadata problem. It's naturally sharded per-container, but solving sharding problems will take a lot of time, so for v1 we can just have it centralized (which naturally limits per-network ops/s). It's processed off-chain, but ordered on-chain.

Describe the solution you'd like

• https://github.com/nspcc-dev/neofs-node/pull/2802
• https://github.com/nspcc-dev/neofs-api/issues/299
• https://github.com/nspcc-dev/neofs-sdk-go/issues/589
• https://github.com/nspcc-dev/neofs-node/issues/2876
• https://github.com/nspcc-dev/neofs-contract/issues/412
• https://github.com/nspcc-dev/neofs-contract/issues/413
• https://github.com/nspcc-dev/neofs-api/issues/300
• https://github.com/nspcc-dev/neofs-contract/issues/414
• https://github.com/nspcc-dev/neofs-node/issues/2877
• https://github.com/nspcc-dev/neo-go/issues/3493
• https://github.com/nspcc-dev/neo-go/issues/3494
• https://github.com/nspcc-dev/neo-go/issues/3496

To be continued.

• 2935