Multiple jobs running on Flink session cluster reuse the persistent Python environment.

I'm running TFX pipelines on a Flink cluster using Beam in k8s. However, extra python packages passed to the Flink runner (or rather beam worker side-car) are only installed once per deployment cycle. Example:

1. Flink is deployed and is up and running
2. A TFX pipeline starts, submits a job to Flink along with a python whl of custom code and beam ops.
3. The beam worker installs the package and the pipeline finishes succesfully.
4. A new TFX pipeline is build where a new beam fn is introduced, the pipline is started and the new whl is submitted as in step 2).
5. This time, the new package is not being installed in the beam worker causing the job to fail due to a reference which does not exist in the beam worker, since it didn't install the new package.

I started using Flink from beam version 2.27 and it has been an issue all the time.