Config to change the default behavior of the schema configuration

[AccsoSG]

Is your feature request related to a problem? Please describe.
The new options for schema configuration with the directives "query", "mutation", "subscription", as well as "selectable", "settable" and "relationship" are a real help. Thanks for the great features!

However, we have a large schema with many types and relationships. This generates a huge schema, much of which is actually not needed or even actually not wanted. With the new directives you can turn all this off, but of course it would be nice if you could customize the default behavior of the directives via a config.

For example, I'm thinking of the following: I would like to prevent the nested creation of objects in general. In the default behavior the nestedOperations property of the relationship directive allows everything for now. I would have to modify hundreds of relationship directives to meet my requirement. More precisely, I would like to customize the default behavior to have a very limited API for now. By explicit configuration I can then extend the API in certain places. For specific relationships I could allow the nested creation of objects.

Describe the solution you'd like
Maybe an extension of the Neo4jFeaturesSettings would be the right place for this.

[MacondoExpress]

Hi @AccsoSG , It's good to hear that the new Schema Configuration directives are already in use!
We also agree to move towards an opt-in solution, we're going in that direction in the 4.0.0 branch where we will have some breaking changes like the aggregations that are no longer generated by default. We wanted to let users get used to these directives and then slowly move to an opt-in approach in the future versions of the library. We have also been considering allowing users to configure the default types generated using Neo4jFeaturesSettings at some point in the future although this isn't an immediate priority.