BUG: rowLabels and colLabels args in pandas.plotting.table have no effect (#37811)
- [ ] closes #37811
- [ ] tests added / passed
- [ ] passes `black pandas`
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] Pass `rowLabels` and `colLabels` args to `plot_backend.table`. Docs improved: the descriptions of `rowLables` and `colLabels` added to their own entries in the docstring.

This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. closing as stale. if you want to continue, pls ping and can re-open. Its a shame that such a trivial fix to a modestly common bug stalled out like this, one that just bit me hard today. @EvsanDlg if you don't object, I'd be willing to add a test, cherrypick `4fb57b2` as a starting point (so you get commit credit), and add types to everything plus any other housekeeping (changelog entry, etc), presumably in a new PR. 

A few pandas-specific questions on the finer details of your conventions and style:

@ivanovmg @jreback Is there a reason `test_table` uses the `_check_plot_works` helper for `DataFrame.plot(table=True)` but not `pandas.plotting.table` (as @EvsanDlg demonstrates in their example)? Also, just to confirm since I couldn't find it in the docs, is `unittest.mock.patch` the canonical pandas way of mocking/patching (vs. e.g. monkeypath, pytest-mocker, etc), and from `from unittest.mock import patch` the standard pandas convention for importing it (vs import `unittest.mock` and referring to it explicitly)?

Also, @jreback should this get a versionchanged marker, so users understand these arguments are non-functional in prior versions of pandas? If so, any particular guidance on phrasing? Thanks! @CAM-Gerlach, ``_check_plot_works`` does more than simply run a plotting function: it ensures that the figure is closed afterwards, that it is saveable and that the returned object is of the correct type.

Since my previous comment here on the use of ``unittest.mock.patch`` I attempted to submit a PR, where I used mocking. It got rejected by the CI. If I remember correctly, it seemed that the CI did not like the use of ``patch`` (I'm not sure whether it was because of importing it in particular way, or just ``patch`` was banned, period).

Throughout the code base I saw the use of ``monkeypatch`` in multiple places, though.
Thus, my comment on ``unittest.mock.patch`` should be reconsidered.
I am not sure if using ``monkeypatch`` one can check whether ``matplotlib.pyplot.table`` was called correctly.