**What happened**:

With the new Backport providers, when calling `DataflowCreatePythonJobOperator` with an empty `py_rerquirments` Dataflow commands always launch inside a virtualenv.

**What you expected to happen**:

The Dataflow command should run locally.


airflow/providers/google/cloud/hooks/dataflow.py
self,
        project_id: str,
        job_name: Optional[str] = None,
        job_id: Optional[str] = None,
        location: str = DEFAULT_DATAFLOW_LOCATION,
    ) -> None:
        """
        Cancels the job with the specified name prefix or Job ID.
        Parameter ``name`` and ``job_id`` are mutually exclusive.
        :param job_name: Name prefix specifying which jobs are to be canceled.
        :type job_name: str
        :param job_id: Job ID specifying which jobs are to be canceled.
        :type job_id: str
        :param location: Job location.
        :type location: str
        :param project_id: Optional, the GCP project ID in which to start a job.
            If set to None or missing, the default project_id from the GCP connection is used.
        :type project_id:
        """
        jobs_controller = _DataflowJobsController(
            dataflow=self.get_conn(),
            project_number=project_id,
            name=job_name,
            job_id=job_id,
            location=location,
            poll_sleep=self.poll_sleep
        )
        jobs_controller.cancel()