[Bug] Prevent hot-reload of workflow definitions from disk

A Python worker reloads the workflow definition from disk every time a new workflow run is started, i.e. without requiring the worker process to be shutdown and restarted. So for example, a long-running workflow that CANs will "hot reload" like this on every CAN, and a non-sticky worker will hot-reload on every WFT.

This is a side-effect of implementation (worker sandboxing involves disabling import cache which results in re-reading from disk) rather than being desired behavior, and isn't appropriate in production worker deployments since users are likely to expect that during deployments they can overwrite files without any modifications to running processes until process restart.

So, let's find a good way to prevent the behavior. For example, one possibility might involve permitting the re-read-from-disk to continue, but having the worker copy the relevant files somewhere private, and importing workflows from there.

Non sono indicati file o test. Inizia tracciando il sandboxing del worker Python e il comportamento della cache degli import descritti nell’issue, quindi valuta come vengono caricate le definizioni dei workflow nelle esecuzioni ripetute. Il lavoro è completato quando un worker in esecuzione mantiene invariato il proprio codice del workflow fino al riavvio del processo del worker, anche per i worker di lunga durata e i worker non sticky.