Update benchmarks for Python 3.12

[movermeyer]

What are you trying to accomplish?

Updating the benchmarking metrics in the tables.

What approach did you choose and why?

Ran the benchmarking scripts.

I had to exclude pendulum and maya (which uses pendulum) since pendulum won't build on Python 3.12 until v3.0.0 comes out (any day now???): sdispater/pendulum#696

tox no longer supports Python < 3.7, so it isn't useful for that anymore.
This means that the Python 2.7 data hasn't been updated. 😞

What should reviewers focus on?

There should be no changes to the Python 2.7 column. I had to manually insert this data, so that's the spot that's most likely to have broken, though I've double-checked.

The impact of these changes

Users can see our Python 3.12 performance numbers and feel that we are keeping up with modern Python.

[movermeyer]

pytablewriter v1.0.0 dropped these, so I replaced them with the new names: thombashi/pytablewriter@7777033

[AlecRosenbaum]

Not a huge deal, but on the second table the extra column makes the table wider than the page will go (and looks cut-off):

The relative speeds are probably most important to at a glance, so maybe those should be the first column before the python versions? (Absolutely not a strong opinion here, just figured I'd mention it)

[movermeyer]

Not a huge deal, but on the second table the extra column makes the table wider than the page will go (and looks cut-off):

@AlecRosenbaum Very true. I've switched the order of the columns so that the relative speed-up is the second column.

---

Aside: for my future reference:

As for making the columns thinner, I thought about changing Incorrect Result to ❌ and having a tooltip to explain what the symbol meant. The only way that I found to get GitHub to render it was using the ..raw: html block in the cell:

.. table::

  +--------------------------------------------------------+
  |             Result                                     |
  +========================================================+
  |.. raw:: html                                           |
  |                                                        |
  |   <span title="Incorrect Result (``None``)">❌</span>  |
  +--------------------------------------------------------+

Which works, but but pytablewriter doesn't support multi-line values in table cells.. 🤷

[movermeyer]

Alright, instead of changing the column order (I was partial to what we had), I've done the simple change of changing the Incorrect Result to ❌, without a tooltip. The columns fit once again:

[movermeyer]

Reduced width so that the columns all fit without a scroll bar.

[movermeyer]

But of course, the table width shown in PR review is not the same as shown on the project main page 🤦:

so the column re-ordering will be necessary (unless we drop some columns)