metadata should be backwards compatible for remote schemas (fix #1120)

[ecthiender]

Description

What component does this PR affect?

• Server
• Console
• CLI
• Docs
• Community Content
• Build System

Requires changes from other components? If yes, please mark the components:

• Server
• Console
• CLI
• Docs
• Community Content
• Build System

Related Issue

#1120

Solution and Design

Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Docs update
• Community content

Checklist:

• I have read the contributing guide and my code conforms to the guidelines.
• This change requires a change in the documentation.
• I have updated the documentation accordingly.
• I have added required tests.

[hasura-bot]

Review app for commit b65a2c4 deployed to Heroku: https://hge-ci-pull-1121.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1121-b65a2c4

[hasura-bot]

Review app for commit 02bc147 deployed to Heroku: https://hge-ci-pull-1121.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1121-02bc147

[shahidhk]

Should we also add some tests for these?

[hasura-bot]

Review app for commit 4c03259 deployed to Heroku: https://hge-ci-pull-1121.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1121-4c03259

[hasura-bot]

Review app for commit fbb15e4 deployed to Heroku: https://hge-ci-pull-1121.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1121-fbb15e4

[hasura-bot]

Review app https://hge-ci-pull-1121.herokuapp.com is deleted