Accept optional parameters to help reduce the output (add a way to output a string format for the ABTs, add a way to exclude properties, etc) according to the syntax document:

The extra parameters are optional and explicitly excluded from the stable API. They are meaningful only when the verbosity is set to queryPlannerDebug and result in an error if provided alongside other verbosities:

• When internalIncludeProperties is false, the “properties” attached to each stage will be omitted.
• When internalPlanFormat “string” is specified, the ABT under each optimizer phase will be represented in a stringified form.
• When internalIncludePhases is specified, only the phases listed will be included in the output.

In this ticket we should consider how verbosity, internalCascadesOptimizerExplainVersion, and internalPlanFormat interact to determine the explain output. A relevant piece of code is here.