Separate engine workflow depending on whether nested mutations are on/off

[ayush3797]

The purpose of the issue is to track the efforts needed for
a) Consuming the feature flag fields in the config file
b) Adding different code paths in the engine based on whether the feature flag is enabled or disabled

[JerryNixon]

The content of this issue has no grammatical errors! ;)

[JerryNixon]

The reasoning around this issue includes giving the ability for developers to avoid any startup cost associated with nested mutations. Developers can already change read/write permissions of entities which can effectively disable mutations. The nuance here is that disabling them globally can mean the engine doesn't have to compute the schema at startup. Please refer to #1950

[severussundar]

The reasoning around this issue includes giving the ability for developers to avoid any startup cost associated with nested mutations. Developers can already change read/write permissions of entities which can effectively disable mutations. The nuance here is that disabling them globally can mean the engine doesn't have to compute the schema at startup. Please refer to #1950

Thank you for adding this. Updated the description.

When the feature is disabled, the schema will be generated the way it is right now; thus avoiding additional computations, memory utilized etc.

[seantleonard]

Follows up the work from #1950