Hasura Metadata generation can cause unwanted diffs

[WonderPanda]

When writing out metadata using js-yaml the ordering of properties is different compared to what is generated by Hasura.

In order to address this logic will be added to only write out metadata if an actual logical change has been detected in one of the managed objects instead of doing it proactively every time the module is booted up

[WonderPanda]

It turns out that we can get 99.9% of the way there by just explicitly constructing the Javascript objects with the same key order as what is generated by Hasura,

The only difference now is in how multi line strings are managed. js-yaml uses the >- prefix. Its not clear yet whether its worth spending time trying to correct this

[github-actions]

This issue is stale because it has been open for 30 days with no activity.