Fix params passing to TaskFlow tasks run with CLI

[vemikhaylov]

Params passed to the TaskFlow tasks using the CLI airflow tasks test command aren't worked correctly (see the linked issue for the more details and examples). This PR is to fix it.

closes: #28287

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[vemikhaylov]

I'm not 100% sure that this is the best place to override this. Probably the args should rather be overridden somewhere closer to execute (e.g., https:/apache/airflow/blob/main/airflow/operators/python.py#L174).

I lack clear understanding what params are / should be used for as opposed to op_args and op_kwargs, so overriding here looked like a safer change to me.

[vemikhaylov]

It wasn't clear to me if a specific case was intended to be tested here originally with the usage of the params name here, which is also a name of the task.params attribute or it's just a coincidence.

I moved it to a simpler structure. If the original one made sense and is needed as well, please let me know, I'll restore it.

[uranusjr]

I don’t think this is correct. Params are params, and different from arguments to the task function. You can access params in a taskflow task like this:

@task
def my_task(params=None):
    # At runtime 'params' holds the params.

[potiuk]

Agree with @uranusjr

[vemikhaylov]

Hey @uranusjr and @potiuk! Thank you a lot for the feedback and providing a link to the docs, I've learned something new!

So from what you mentioned above, if I understand it correctly, params seems to be a different parallel concept to the tasks args and the current behaviour is correct, right?

Is the issue #28287 not completely correct and not a bug, but rather a feature request then? In other words, do we still want to have a way to pass args to a task run with the CLI command airflow tasks test (e.g., passing --task-kwargs)?