docs(changeset): Massive overhaul of the behavior system which now ha…

…s a centralized registry of

known behaviors and applies behaviors in a more careful and nuanced way,
removing many hacks and workarounds, and ultimately meaning that
`defaultBehavior: "-*"` should now operate correctly.

Technically this is a breaking change because the order in which behaviors are
applied has changed, and so a different behavior might ultimately "win". This
shows up in places where there is ambiguity, for example if you add
`@filterable` to a function that you don't have execute permissions on, that
function will now show up in the schema since user overrides (smart tags) "win"
versus inferred behaviors such as introspected permissions; this wasn't the
case before. Hopefully most users will not notice any difference, and for those
who do, the `graphile behavior debug` CLI may be able to help you figure out
what's going on.

Be sure to print your schema before and after this update and look for changes;
if there are changes then you likely need to fix the relevant behaviors/smart
tags. (Hopefully there's no changes for you!)

.changeset/modern-bananas-drop.md

@@ -0,0 +1,24 @@
+---
+"graphile-build-pg": patch
+"graphile-build": patch
+"postgraphile": patch
+---
+
+Massive overhaul of the behavior system which now has a centralized registry of
+known behaviors and applies behaviors in a more careful and nuanced way,
+removing many hacks and workarounds, and ultimately meaning that
+`defaultBehavior: "-*"` should now operate correctly.
+
+Technically this is a breaking change because the order in which behaviors are
+applied has changed, and so a different behavior might ultimately "win". This
+shows up in places where there is ambiguity, for example if you add
+`@filterable` to a function that you don't have execute permissions on, that
+function will now show up in the schema since user overrides (smart tags) "win"
+versus inferred behaviors such as introspected permissions; this wasn't the case
+before. Hopefully most users will not notice any difference, and for those who
+do, the `graphile behavior debug` CLI may be able to help you figure out what's
+going on.
+
+Be sure to print your schema before and after this update and look for changes;
+if there are changes then you likely need to fix the relevant behaviors/smart
+tags. (Hopefully there's no changes for you!)