Enhance Tableau Operator Logging with Human Readable Object DetailsTableau log in detail

[sandeepmandal70]

Linked Issue

Closes: #49671

Description

This PR enhances the observability of Tableau workflows by improving logging within the TableauOperator.

Previously, Airflow logs only displayed Tableau object LUIDs (IDs) when a matching resource was found. This made it difficult for users and developers to identify which Tableau content (e.g., workbook, datasource) was being processed during execution.

To improve visibility, additional log lines have been added immediately after the existing resource ID log message. These new lines display user-friendly object details, including resource name, folder/project, and a direct URL to the Tableau content on Tableau Server or Tableau Cloud.

Before
self.log.info("Found matching with id %s", resource_id)

After

self.log.info("Found matching with id %s", resource_id)
self.log.info("Resource object : %s", resource)
self.log.info("Content Name : %s", resource.name)
self.log.info("Content Folder : %s", resource.project_name)
self.log.info("Content URL : %s", resource.webpage_url)

Benefits

• Improves log readability by including meaningful Tableau content details.
• Enables operators and developers to quickly identify which Tableau assets are processed during job runs.
• Provides a direct clickable URL for quick navigation and validation on Tableau Server/Cloud.
• Does not change any existing behavior it only enhances logging output.

Testing Done

• Tested locally by triggering various Tableau jobs.
• Verified that logs now display:

• Resource object details
• Content name and project folder
• Direct Tableau content URL

• Confirmed that existing functionality and job execution remain unaffected.

This enhancement provides developers and data engineers greater transparency during Tableau workflow execution.
The Content URL in particular enables faster troubleshooting by allowing direct access to the corresponding Tableau resource without manually searching for it.

---

^ 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 airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack