#2089 makes a breaking change to field config behavior

[taion]

By no longer passing through other unknown properties to field configurations, #2089 introduces a small breaking change to behavior.

Previously, integrations like https://github.com/4Catalyzer/graphql-validation-complexity#usage could enable additional field configuration just by specifying other fields. Now, against 14.5.0, this no longer works.

It would be great if we could temporarily revert this change, then increment the major version to v15 to make this change.

[taion]

@IvanGoncharov With respect to #2089 (comment), I very much agree that this change should be made. It's just that, for the sake of compatibility, I don't think this should happen on a non-major version bump.