Docs: fix example to use task context and logger instead of dag.log (#54380)

[prdai]

Summary

This PR fixes a documentation bug in the "Params" example under core-concepts: the use of dag.log inside the @task.python function. In the current code, dag.log doesn’t exist in TaskFlow DAGs, causing runtime errors when the code is executed.

Changes

• Replaced dag.log.info(...) with proper usage of task context and Python logging:
  • Used get_current_context() to access runtime values.
  • Used a standard logger (logging.getLogger("airflow.task")) to output parameter values.

- dag.log.info(dag.params['my_int_param'])
+ logger.info(ctx["dag"].params["my_int_param"])

And similarly for user-provided values via params.

Rationale

• Airflow 3's Task SDK no longer attaches a .log property to DAG, so relying on dag.log is no longer valid.
• get_current_context() provides a reliable way to access dag.params and params inside tasks.
• Logging via Python’s logging module (or self.log on operators) aligns with Airflow’s logging model and avoids missing attribute errors.

Fixes

Closes: #54380.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test