Disallow groovy script in SQL statements to prevent possible exploitation.

We would like to disable the ability to run groovy scripts in SQL statements with an option to enable groovy scripts by setting a configuration variable.

The issue names no files, tests, or entry points. Start by locating SQL statement handling and the configuration system that governs optional features, then trace how Groovy scripts are executed. Done means Groovy execution is disabled by default, can be explicitly enabled through configuration, and the behavior is covered by tests.

Written by the indexing model from the issue text.