In highly secured deployments the general advice is to not approve any signature, so the "Use Groovy Sandbox" checkbox does not make sense (as it should be always checked). Disabling it might end up in non-runnable pipelines (as signature approvals won't be accepted anyways).

This issue is to add a global configuration to hide this checkbox from the UI of pipeline jobs definition, which will hopefully avoid confusion on users with just `Item.CONFIGURE`.