Enable stabilization of objects/lists going through loadMany/loadOne multistep

[benjie]

Description

Fixes https://github.com/graphile/crystal/issues/2170

Performance impact

Marginal performance cost for loadOne/loadMany calls that accept object/list specs.

Security impact

Generally an improvement I hope, though there's a risk of memory exhaustion attacks if this is not used sensibly.

Checklist

• [x] My code matches the project's code style and yarn lint:fix passes.
• [x] I've added tests for the new feature, and yarn test passes.
• [ ] I have detailed the new feature in the relevant documentation.
• [x] I have added this feature to 'Pending' in the RELEASE_NOTES.md file (if one exists).
• [ ] If this is a breaking change I've explained why.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: b77f6e909c1c0f1921f75726384472e945ea698b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

| Name | Type | | -------------------------- | ----- | | @dataplan/pg | Patch | | grafast | Patch | | graphile-build-pg | Patch | | graphile-utils | Patch | | pgl | Patch | | postgraphile | Patch | | @localrepo/grafast-bench | Patch | | @dataplan/json | Patch | | @grafserv/persisted | Patch | | grafserv | Patch | | ruru-components | Patch | | @localrepo/grafast-website | Patch | | graphile-build | Patch | | graphile-export | Patch | | graphile | Patch |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR