Hey! I have a question on order returned in the read-schema endpoint. In serverless or running spicedb locally in docker for testing, when I read the schema, it always returns in the order it was written in (ie the resources defined in the schema are returned in the order that we specify in the writeSchema request), however when trying a read-schema request to a self-hosted instance of spicedb on a remote server, the schema is not returned in order - wondering if this is something to do with different versions of the container/client/database, or if somewhere in the serialization layer the order is changed? I'm not super familiar with grpc etc so maybe order is not expected to be guaranteed? I have automation built around the first line of the schema containing a version number so this breaks that automation, so I'm wondering if I will need to change the automation to cater for this, or if it's unexpected behaviour and something else could be going on. Also side note - is there a way to revert to no schema defined?