[dagster-tableau] Use tableauserverclient

[maximearmstrong]

Summary & Motivation

Updates dagster-tableau to use tableauserverclient instead of requests.

Our first implementation leveraged requests, as suggested in their Tableau REST API documentation website and samples, see here and here.

Tableau provides a python client for their APIs, which is not mentioned on their REST API documentation website, but can be found here, docs here.

The library seems to be maintained only a few times a year, but the main reasons for using tableauserverclient instead of requests are:

• all their endpoints are already implemented.
  • Some of their endpoints support JSON, some other only XML. Using the library makes it easier to handle the edge cases.
• Using requests and following their documentation here and here, I wasn't able query their update workbook now endpoint without receiving a HTTP error 400 without much information to troubleshoot.
  • According to the forum discussions, it is known by the community that some examples won't work, but that using the client works well.

Note: the subsequent PR will require this change to allow users to refresh their workbooks.

How I Tested These Changes

BK with updated tests

Changelog

NOCHANGELOG

• NEW (added new feature or capability)
• BUGFIX (fixed a bug)
• DOCS (added or updated documentation)

[maximearmstrong]

• [dagster-tableau] Update docs with refreshable workbooks and materialization #24864
• [dagster-tableau] Implement refreshable workbooks #24862
• [dagster-tableau] Use tableauserverclient #24826 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @maximearmstrong and the rest of your teammates on Graphite