Enable to check package documentation can be built without producing
sphinx warnings.

The sphinx environment is designed to be used in continuous integration
in order to prevent breaking documentation build when committing changes.

The sphinx-dev environment is designed to be used inside a full swh
development environment.

Related to T3258

The "Save code now" Web UI form was using an internal dedicated endpoint
to submit an origin save request.

That endpoint is redundant with the /origin/save Web API one so drop
it and use Web API instead.

The internal endpoint was there to validate the CSRF token injected
by Django but the /origin/save already has a rate limit of 10 POST
requests per hour to prevent abuse.

They are rendered as an epoch date instead of not being displayed. The following
bypasses the transformation if the value is null. In effect, such value should no longer
be displayed.

Related to T3296

requests-mock recently changed its way to match URLs, paths are now
quoted when registering mocked URLs.

As Web API graph endpoint send HTTP requests to the Graph service
with SWHIDs in URL paths (containing ':' characters), those must
also be quoted or recent requests-mock will not find the registered
mocked URLs.

Also ensure tests still pass with older requests-mock versions.

See https://github.com/jamielennox/requests-mock/commit/f072845

For consistency with the recent renaming in swh-graph

This introduces a new endpoint to refresh the status of the save code now requests. This
endpoint will be called periodically. That concern is out of scope of the listing ui and
source of status update desynchronization [1]

The listing ui now feels more immediate as implementation wise, it no longer writes when
actually listing rows.

This slightly improves the code by typing it a bit more. A new SaveOriginRequestInfo got
added to represent the save origin request to display view side. This matches what
other views manipulates.

[1] T3278#63827

Related to T3280

An invalid value was generated for the path query parameter of the
revision view, leading to a 404 error.

Also add missing tests for some SWHIDs resolving.

Related to T3279

related to T3251

Pytest report when building debian package is not easily exploitable
without silenting that warning.

The use of django-test-migrations have some unexpected side effect
when building the debian package of swh-web, some default data
added to the SaveAuthorizedOrigin table in initial migrations
end up missing.

So ensure to explicitely fill that table with needed tests data
to avoid some test failures.

Related to T3266

Related to T3266

As demonstrated in the following snapshot, just placed prior to arguments [1]. So this
is read soon enough by users who wants more details.

[1] https://forge.softwareheritage.org/F4420335

Related to T3266

Related to T3266

Related to T3266

Its content has been merged into the root conf.py file in swh-docs.

Related to T3258

The _hljs_languages* global variables content rely on reading a JSON file
located through Django static finders.

As a side effect, when the module is imported, the JSON file is located
then read.

When the DJANGO_SETTINGS_MODULE environment variable is not set, the
module import will fail as the JSON file could not be located.

So avoid to execute that JSON loading code when importing the module
by turning the global variables into functions.

The purpose is to avoid import errors when running sphinx autodoc.

Related to T3266

Legacy SWHID browse URLs were no more honored, new ones were used
instead resulting in SWHID validation errors.

Related to T3234

Check a SWHID entered in a search input is valid by sending a request
to the resolve endpoint of the Web API.

If the SWHID is not valid, precise parsing error will be extracted from
the Web API response and displayed in the Web UI to indicate the search
form can not be validated.

Related to T3247

It enables to avoid getting an invalid SWHID when removing the
URL prefix.

Related to T3234

```
Defining 'pytest_plugins' in a non-top-level conftest is no longer supported:
It affects the entire test suite instead of just below the conftest as expected.
  /home/dev/swh-environment/swh-web/swh/web/tests/conftest.py
Please move it to a top level conftest file at the rootdir:
  /home/dev/swh-environment/swh-web
For more information, visit:
  https://docs.pytest.org/en/stable/deprecations.html#pytest-plugins-in-non-top-level-conftest-files
```

As a consequence, minimum required node version is now 12.x.

- Add an option to configure a swh-counters backend
- Add an object to choose where to route the counter stats queries

The default behavior is kept as long as the counters_backend property is
not configured

Related to T3231

The data loaded by the webapp is a mix of of static file
issued from an old munin and live data from prometheus.
These points can be added to the static file so the graphs
will only depends of the content of json loaded
at `history_counters_url`

Related to T3232

This only deals with the finalized save code now statuses (succeeded, failed) as it's
the only information referenced in the model.

Related to T1481

A Web API bearer token will expire after 30 days of inactivity.

So when a user tries to display a previously generated token from the
dedicated Web UI, check its validity and display an error message if
the token has expired.

Related to T3121

This is more consistent to organize web assets sources and
configuration this way.

Freshly released docutils 0.17 produces a different HTML output
than its previous version so ensure to have a rst input that
produces the same HTML output with all docutils versions.

When using the PostgreSQL backend for django database, models.BinaryField
colums are typed to memoryview while they are typed to bytes with
SQLite backend.

So handle both token types to fix errors in production since the
move to PostgreSQL backend.

When browsing an object in a revision context without any branch or release
name, set the branches dropdown button text to "Revision: <rev_id>" instead
of "Branch: <rev_id>".

Previously the SWHID resolver was trying to associate a branch name to
a revision by checking tip revisions in snapshot branches list.

That operation is not really needed, can be costly to execute and can
lead to regressions in SWHID resolving so remove it.

Related to T3195