Update runnable schema in runtime when provider app changes version

[gris]

What is the purpose of this pull request?

Update graphql runnable schema in runtime when a new version of a provider app is installed in the same workspace.

What problem is this solving?

It stops breaking the store when a new field is added and called by a store.

How should this be manually tested?

You can use this workspace that already has a modified graphql schema, and link a new version of search-graphql and add new fields.

This contribution depends on this one, which is deployed.

Screenshots or example usage

To test in other workspace:

• Link the branch in the above PR of graphql-server
• Do a yarn link on the graphql resolver of your choice (and yarn watch)
• link your new version of the provider app and add fields

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[klzns]

Tested in my own workspace without the code linked which triggered the error.

Linked all the code in my workspace, and rerun the query and it worked fine 👍

Steps:

1. vtex link with https://github.com/vtex/graphql-server/pull/251
2. Open a terminal with this code and run yarn, yarn build and yarn link
3. Open a terminal with search-resolver@1.x and run yarn link @vtex/api inside the node folder, and then vtex link
4. Open a terminal with search-graphql add a new field in the Product type and query it in the GraphQL IDE just like the example bellow:

https://breno--demostore.myvtex.com/_v/private/vtex.search-graphql@0.30.0/graphiql/v1?query=%7B%0A%20%20products(query%3A%22coffee%22)%7B%0A%20%20%20%20productId%0A%20%20%20%20productName%0A%20%20%20%20novo%0A%20%20%7D%0A%7D

[Jeymisson]

LGTM would wait for @tlgimenes review