### Apache Airflow version

2.6.3

### What happened

When the condition in ```ShortCircuitOperator``` is truthy it is returned at
https://github.com/apache/airflow/blob/a2ae2265ce960d65bc3c4bf805ee77954a1f895c/airflow/operators/python.py#L252
but when it is falsy, the function falls through without returning anything.

If ```multiple_outputs``` is set ```true``` (with for example ```@task.short_circuit(multiple_outputs=True```) ```_handle_output``` of
```DecoratedOperator``` at
https://github.com/apache/airflow/blob/a2ae2265ce960d65bc3c4bf805ee77954a1f895c/airflow/decorators/base.py#L242
does not test for None and raises at
https://github.com/apache/airflow/blob/a2ae2265ce960d65bc3c4bf805ee77954a1f895c/airflow/decorators/base.py#L255
This makes it impossible to pass a falsy value (i.e. an empty dictionary) so ```ShortCircuitOperator``` is unusable with ```multiple_outputs=true```


### What you think should happen instead

Probably the ```xcom_push``` should not be attempted with ```None```, or possibly the condition should be returned by ```ShortCircuitOperator``` even if it is falsy

### How to reproduce

```python
@task.short_circuit(multiple_outputs=True)
def test():
  return {}
```

### Operating System

Ubuntu 22.04.2 LTS

### Versions of Apache Airflow Providers

_No response_

### Deployment

Official Apache Airflow Helm Chart

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"""
    Run a function in a virtualenv that is created and destroyed automatically.
    The function (has certain caveats) must be defined using def, and not be
    part of a class. All imports must happen inside the function
    and no variables outside the scope may be referenced. A global scope
    variable named virtualenv_string_args will be available (populated by
    string_args). In addition, one can pass stuff through op_args and op_kwargs, and one
    can use a return value.
    Note that if your virtualenv runs in a different Python major version than Airflow,
    you cannot use return values, op_args, op_kwargs, or use any macros that are being provided to
    Airflow through plugins. You can use string_args though.
    .. seealso::
        For more information on how to use this operator, take a look at the guide:
        :ref:`howto/operator:PythonVirtualenvOperator`
    :param python_callable: A python function with no references to outside variables,
        defined with def, which will be run in a virtualenv
    :param requirements: Either a list of requirement strings, or a (templated)
        "requirements file" as specified by pip.
    :param python_version: The Python version to run the virtualenv with. Note that