Bump actions/setup-python from 4.6.0 to 4.6.1

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4.6.0 to 4.6.1.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v4.6.0...v4.6.1

)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Mark tests as requiring setuptools in tox.ini and setup.py

test_client.py uses pkg_resources. That's part of setuptools,
not Python. Per
https://docs.python.org/3.12/whatsnew/3.12.html#removed

 , it
was previously included by default in venv environments, but no
longer is from 3.12 onwards, so we need to explicitly require
setuptools to ensure it's available.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

Bump actions/setup-python from 4.5.0 to 4.6.0

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4.5.0 to 4.6.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v4.5.0...v4.6.0

)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

API calls: raise original exception when retries exhausted

This is an alternative approach to solve the problem identified
in #279 . When doing API calls with `retry_on_error` set to
true (the default), if the call fails after all retries are
exhausted, we raise our own `MaximumRetriesExceeded` exception,
which tells you nothing about what actually went wrong, just
that we exhausted the retry count. It seems much more useful
to raise an exception with information about why the connection
is failing.

This changes that behaviour so that, on most paths, we would
raise an appropriate exception from requests (either the one
we caught, or an HTTPError via `raise_for_status`) if we exhaust
the retry count. Only if we fail due to database lag would we
still raise `MaximumRetriesExceeded` (because there isn't really
an underlying exception we can handily raise in that case).

Note that it was already possible to hit
`stream.raise_for_status()` before this change, if the status
code was outside the 500 range, so in theory callers should
already be prepared for that. It was not possible to get a
`requests.exceptions.ConnectionError` or
`requests.exceptions.Timeout` with `retry_on_error` true, though,
so this is genuinely a behaviour change on that front.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

Handle page protection having no expiry (#290)

Issue #290 gives an example of a wiki with protected pages whose
protection definitions have no 'expiry' key at all. This seems
strange and, on a quick through the mediawiki code, difficult
to achieve, but since there's a live site out there that does it,
and mediawiki *does* seem to have at least some code to handle
such cases (e.g. how the expiry shows as 'indefinite' in the
page information), let's handle it too, by representing this as
None.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

Add/Update some documentation

Document how to connect using a proxy

Add mime to imageinfo

Add move_subpages, ignore_warnings to page.move

Improve and fix Site.expandtemplates

Fix tests

It seems that pytest-cov does not collect any coverage without
this file.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

This fails at least when run via tox on current Fedora, flake8
tries to parse the # as a directive and chokes on it.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

`clientlogin()` does `self.require(1, 27)`, which needs the site
instance's `version` attribute to be set, but this is usually
done by `site_init()`, which is mocked out in the tests. We can
fix the problem by just manually setting a sufficiently high
version in the tests.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

This is a missing bit of the CI enablement, per
https://github.com/ymyzk/tox-gh-actions

 . I hope this will make
the Python 3.6 tests run properly.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

This drops the travis-ci config and adds config for running tests
via tox in Github Actions. It also updates the list of envs in
tox.ini for recent Python 3 versions.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

Always available through the 2.7 and 3+ stdlib

Not required as `logging.NullHandler` is available on all supported python versions

mock was included in unittest in python 3.3