findDangerousChanges: sort fields inside 'defaultValue'

[IvanGoncharov]

Fixes #2150

[IvanGoncharov]

For input type default values we apparently just compare it's stringified value instead of doing a deep comparison.

@Neitsch It's intentional since we want to detect only changes observable by the client.
So we should compare defaultValues in the same representation as used by introspection:

graphql-js/src/type/introspection.js

Lines 337 to 345 in 0d2220f

	defaultValue: {
	type: GraphQLString,
	description:
	'A GraphQL-formatted string representing the default value for this input value.',
	resolve(inputVal) {
	const valueAST = astFromValue(inputVal.defaultValue, inputVal.type);
	return valueAST ? print(valueAST) : null;
	},
	},

It's important because defaultValue is always specified in "internal" format (same format as returned by parseLiteral/parseValue and passed into serialize) that mean it can be for example instances of Date class and === wouldn't work for them but if you pass both values into serialize you can compare resulting strings without any problems.

[IvanGoncharov]

@mrtnzlml @Neitsch Thanks for a quick review 👍

[mrtnzlml]

Thanks for the fix. It was really fast! :)

[IvanGoncharov]

@mrtnzlml Released in v14.5.5 🎉 sorry for the delay.