### What

This PR rewrites how argument and field presets are handled to address
two final bugs:

* If you define field presets on TypePermissions and that type is used
nested inside an argument's type somewhere, but as an array of the
object type, the field presets will not be applied
* If you define field presets on TypePermissions and your types are
recursive, field presets will only be applied to the first layer and not
past the point where the types recur

These bugs are caused by the argument presets being precalculated during
metadata resolve into field_paths that are used to poke the preset
values onto the arguments. However, this approach fundamentally doesn't
work, since recursive types make any field path infinitely long.

The only way to handle this correctly is to walk the types at query
time, along with the argument values provided by the user, and apply the
field presets. This allows you to walk the types recursively, and is not
infinite, since the recursion is bounded by the value provided by the
user. Walking the types also allows correct navigation of arrays (which
field paths didn't), so the presetting can descend into arrays and apply
presets to the objects inside.

### How

The argument_presets stage has been delete from metadata_resolve.
Instead, argument and field presetting is performed at query time in the
plan stage. This required access to metadata to perform, so metadata
types have been plumbed down into the GraphQL IR processing stage and
then into the argument planning code.

Please look at the comments I've submitted below for further commentary.

---------

Co-authored-by: Daniel Harvey <danieljamesharvey@gmail.com>
V3_GIT_ORIGIN_REV_ID: 362a1d5c2943c2a3837424c327b3e4defb0d600c

### What
Moves the changelog entries from #1542 into unreleased.

V3_GIT_ORIGIN_REV_ID: 10189534a4e68f91f88c928155b2308f9689540f