Right now __read() will stop reading at "OK" even if a ">" is still coming.
This can cause the ">" to be seen as the response to the next command, which
confuses the initialization sequence, since the initialization sequence
expects a very specific set of responses to its commands.

This changes __read() so that by default it only treats ">" as the response
terminator. When we issue the "ATLP" command to enter low-power mode, we will
use "OK" as the response terminator instead, since that's the only time we
don't expect to see a prompt.

This should fix #226 and should also fix #227.

Signed-off-by: Alistair Francis <alistair@alistair23.me>

Signed-off-by: Alistair Francis <alistair@alistair23.me>

Moving to a feature branch

This reverts commit 3ecbf6f.
This reverts commit eb8679e.

Also fixed some of the doc headers for more modern versions of mkdocs

Without this fix, Python 3.13.1 yields this warning during "import odb":

    …/obd/utils.py:177: SyntaxWarning: invalid escape sequence '\C'

I'm not a Windows expert, but the correct naming convention seems to
be described here:

https://support.microsoft.com/en-us/topic/howto-specify-serial-ports-larger-than-com9-db9078a5-b7b6-bf00-240f-f749ebfd913e

Also corrected some of the package classifiers to indicate that this
python library no longer supports python 2. It didn't even with the
older 0.20.* Pint, though Pint itself now only supports python 3.9+

Uprev pint to 0.24.* for python 3.13+ support

setup.py -> pyproject.toml

bumped to 0.7.3