Have required and NonNull true by default at the project level

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to explicitly set required a List field, or any field for that matter. It makes for really frustrating usage of our APIs that rely on typescript types generated by our graphene schema. We have to constantly add unnecessary checks and write more obtuse code just to satisfy our types. On top of that, the way that this typing is done both in python(pyright and I believe others) and in typescript are the exact opposite, you explicitly define that something can be optional. This makes it extremely unintuitive and hard to spot issues until the api starts getting use from our typescript apps.

Describe the solution you'd like
A setting at the root level to have required default to true always se we have to explicitly set required to false. This would also apply to NonNull for list queries which might need a Nullable, or Optional, or allow the required argument for type to work with the list.

Describe alternatives you've considered
I can build new types that extend the existing types and add a linter to make sure none of the original types are being used in future development. It's doable, and I'll end up doing it, but the solution I'm suggesting doesn't feel that farfetched to put in for others who may have this frustration.

Additional context
In typescript if I want to type as an array I can use Array, or [], and it will be an array, it wont expect null and it wont expect undefined. I have to be explicit if the value is nullable or undefined. Similarly in python, with pyright at least, you also have to be making sure to be explicit that the type is optional or nullable.

I'm at the very least curious why required is defaulted to false in the first place.

Commencez par retracer comment les valeurs par défaut required et NonNull sont actuellement déterminées pour les champs et les requêtes de listes, puis identifiez le point d’entrée de configuration au niveau du projet décrit dans la demande. Clarifiez comment required=false explicite et les types de listes nullable ou optionnels devraient remplacer les nouvelles valeurs par défaut, puis ajoutez une couverture pour ces cas avant de considérer la fonctionnalité comme terminée.