Add `run_if`/`skip_if` functionality to non-TaskFlow operators

### Description

Currently, the useful `run_if` and `skip_if` decorators can only be added to tasks that are decorated by the `@task` decorator, aka TaskFlow compatible operators. However, many common operators are not compatible with TaskFlow API, e.g. the `SqlExecuteQueryOperator`. If you try, you will be met with:

```
skip_if can only be used with task. decorate with @task before @skip_if.
```

This request is for `run_if` and `skip_if` to be added to all operators, not just TaskFlow compatible ones.

### Use case/motivation

I want to use `run_if` and `skip_if` for an operator that isn't TaskFlow compatible.

### Related issues

There is a similar issue that I didn't bookmark to make `@task` decorator apply to classes (aka Operators), not just functions. Depending on how that's implemented, it could solve this issue.

### Are you willing to submit a PR?

- [X] 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)

Start by examining the existing run_if and skip_if decorators and how SqlExecuteQueryOperator is handled, then compare that path with @task-decorated operators. Done means both conditional features work for non-TaskFlow operators, including the stated use case, without requiring @task.

Written by the indexing model from the issue text.