Add example global behavior to disable everything by default

[jcgsville]

Description

This is a small addition to the documentation for something that took me several minutes to figure out. It is something I suspect will be useful for others who want to take the same disabled-by-default approach that I am taking with postgraphile

Performance impact

None - just docs

Security impact

None - just docs

Checklist

• I have detailed the new feature in the relevant documentation.
• I have added this feature to 'Pending' in the RELEASE_NOTES.md file (if one exists).

@benjie, I imagine we don't need release notes for documentation tweaks?

[changeset-bot]

⚠️ No Changeset found

Latest commit: 617ee1c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[jcgsville]

It turns out I'm still getting familiar with the behavior system. Not even sure if I can figure out how to selectively enable the things I want to after using -*, so maybe take this suggestion with a large grain of salt

[jcgsville]

Only after messing with this for an hour or two did I realize that this list is not exhaustive

https://postgraphile.org/postgraphile/next/behavior#core-behaviors

Should probably specify that

[benjie]

This isn’t documented yet because it’s buggy:

• Make defaultBehavior: "-*" work as expected #1803

[jcgsville]

This isn’t documented yet because it’s buggy:

• Make defaultBehavior: "-*" work as expected #1803

Makes sense. I definitely should have skimmed the other open issues first instead of relying on search