[Feature Request]: Allow “variable override” for boolean options (checkboxes) in transform dialogs (e.g., Update

### What would you like to happen?

Background
Several transform boolean options (checkboxes) can only be set statically at design time. Example in Update transform: Use batch updates, Skip lookup, Ignore lookup failure, etc.

Problem
In parameterized pipelines (multi-env: dev/qa/prod, multi-tenant, reusable templates), we need to toggle behaviors without duplicating pipelines/transforms or adding control-flow steps (Switch/If) solely to flip a boolean flag.

Proposal
Add optional variable override support for boolean (checkbox) properties in transform dialogs.

Expected behavior (suggestion):

Keep the checkbox as the base default value.

Add an optional field: “Override by variable” (or a variable icon next to the checkbox).

If the override field is set and the variable is defined:

Resolve at runtime and parse to boolean.

Accept common formats: true/false, Y/N, 1/0, yes/no (case-insensitive).

If the variable is empty/undefined:

Use the checkbox value (predictable fallback).

Log when override is applied (debug/info):
“Update: Use batch updates overridden by ${VAR_NAME}=true”.

### Issue Priority

Priority: 3

### Issue Component

Component: Hop Gui

No files or tests are named. Start by tracing the Update transform dialog and its boolean options, then identify whether the same override behavior must apply to other transform dialogs. Done means a variable can override a checkbox at runtime using the stated boolean formats, falls back when unset, and logs the applied override.

Written by the indexing model from the issue text.