This allows initializing Sentry with the environment the process
is running in (ie. "production" or "staging"), which allows filtering
in the web UI to only show issues happening in one of the environments.

https://docs.sentry.io/enriching-error-data/environments/?platform=python

Related to T2188

This enables tracking of issues by release/package version in sentry
(https://docs.sentry.io/workflow/releases/).

Also deduplicates code used to call sentry_sdk.init by making all our
init code go through the same function swh.core.sentry.init_sentry."

Related to T2110

It was systematically named that way in code.

Having tox call tox is a bit weird, but the alternatives are:
 - duplication of the test command, which is a bit sad
 - replacing all the positive factors with conjunction of negative factors, e.g.
   `core` -> `!db-!server`, which makes the logic painful to follow

One day, tox will have environment aliases which will make this horror moot :-)

(Idea pulled from a comment in https://github.com/tox-dev/tox/issues/427)

The current tests depend on order of execution: if the main tests run before the
db tests, the addition of extra subcommands makes them fail.

Makes it easier to save/restore it in test fixtures.

This requires some more stub-missing entries declared in mypy.ini to pass OK.

swh.storage raises TypeErrors when type checking of incoming objects fails. We
need to make sure that these go through the RPC layer unchanged.

When run under a systemd service, the default stop command is to kill the
process; By default, Python doesn't trap sigterm and terminates the process
immediately, so even finally blocks don't run.

This traps SIGTERM and SIGINT (^C) signals and raises an exception, allowing the
process to exit in an orderly fashion.

for improved readability and control flow understandability

to that end, refactor HTTP status checking logic so that it is reused in
various places

This should allow us to stop playing whack-a-mole with logging configuration
between Celery workers (where the logging configuration is hard-coded in our
initialization routines) and CLI tools (where we only have the log-level knob).

This is useful to document the interaction between options

As mentioned by @anlambert in D2264.

make codespell happy

These values haven't changed since the types have been introduced to PostgreSQL:

https://archive.softwareheritage.org/browse/revision/d31084e9d1118b25fd16580d9d8c2924b5740dff/?path=src/backend/catalog/pg_type.h#L95
https://archive.softwareheritage.org/browse/revision/d31084e9d1118b25fd16580d9d8c2924b5740dff/?path=src/backend/catalog/pg_type.h#L200

This is an issue when swh.model is installed but not dulwich: swh.model.cli
imports dulwich unconditionally, so /usr/bin/swh fails for all subcommands
instead of just ignoring the issue.

When the simplejson module is present in the Phython environment, requests will
use it to decode json but a call to response.json(cls=...) will raise an exception
as the arguments accepted by JSONDecoder are inconsistent between the standard library
json and simplejson (more details here: https://github.com/psf/requests/issues/4842).

So ensure to use standard json module for decoding response texts.