feat: More extensive configuration

[kevinmichaelchen]

This PR introduces a new --config / -c flag, which allows for further customization of pruning logic.

The primary use case here is filtering fields out of certain objects or inputs.

Config File Format

[[type]]
name = "PersonInsertInput"
new_name = "SvcPersonInsertInput"
deny_list = ["address"]

[[type]]
name = "Person"
new_name = "SvcPerson"
deny_list = ["address"]

How it works

The first thing the CLI will do is parse the TOML config file.

• name — The name of a type definition that the config rule will apply for.
• new_name — What we should call the new type definition.
  • Optional. Useful when we need to preserve the original source definition and don't want the two definitions to have a name collision.
• deny_list — The fields we should filter out of the type definition.

Caveats

• Still need to deprecate --desiredDefinitions
• When we prune an object, that may break some of its interface contracts
  • The current implementation just clears all interfaces entirely. Maybe the config file can be responsible for creation of new interfaces, but it's out of scope for now.