Updating origin type counters in coverage widget every hour seems
more reasonable that doing it every 5 minutes as the underlying
database requests are pretty costly.

That function is used to dynamically retrieve the list of origin visit
types (git, svn, npm, ...) currently supported by Software Heritage.

That list of visit types is then used to populate the visit type
dropdown in the search form available in the home and search pages
of the web application.

However getting that visit types list is costly as it involves sending
an elasticsearch query through the use of swh-search.

So instead of sending that costly query each time a search form must
be rendered, prefer to cache the visit types list and update it
every 24 hours.

That change significantly speedup the homepage rendering of the
web application.

Add a decorator enabling to put the result of a function call in Django
cache, subsequent calls will then directly return the cached value.

Use that decorator whenever it is possible in swh-web codebase to simplify
the handling of cached values and improve code readability.

The next version of swh-deposit will do this renaming, for consistency with
_admin_deposit_list and the rest of the codebase.

This function uses the html part if no text part is available. If
multiple plain text or html parts are available, it uses the largest
one.

These utilities allow us to generate addresses of the form
`<localpart>+<integer>.<signature>@<domain>`, where the integer is the
primary key of a given object for which we want to track email
exchanges. The signature prevents the addresses from being forged, that
is, the addresses have to be explicitly generated and displayed by the
web app to be discovered.

The counterpart function retrieves all relevant email addresses from the
list of recipients of an email message, and validates the signatures to
recover the integer values that won't have been tampered with.

These new utilities are expected to be used in the views and signal
handlers pertaining to processing of inbound email messages.

pytest-postgresql 3.1.3 and pytest-redis 2.4.0 added support for
pytest >= 7 so we can now drop the pytest pinning.

This reverts commit ea683ca5.

djangorestframework-stubs 1.5.0 has been released, fixing the observed issue.

It prevents infinite reload of web application in browser when overriding
swh-web sources in docker-compose environment and modifying js sources.

This allows calling the function on a single recipient rather than on a
whole message, when one isn't available.

Other modules still need psycopg2 and pytest-postgresql 4 introduced a
hard dependency on psycopg3.

This restriction has only been needed since a recent dependency
upgrade (or maybe a pip upgrade); pip has stopped being able to solve it
itself for some reason.

as a modal

Related to T4078

Prior to this commit, this was done for all deposits but it's only a good fallback for
typed deposit 'code'.

Related to T4123

Some database tests depend on the text returned by the SQL client, which
is localized. Forcing the C locale ensures the text gets output in
English.

Remove mock fixture from load tests.
Add tests for status update and API failure.
Add tests for mailto email contact.

pybadges v3.0 has recently been released so we can now remove those
workarounds to fix pytest execution as they are no longer needed.

This should alleviate problems in documentation build.

Also, it turns out the add_forge_now apps was misconfigured. This commit fixes that.

In particular, this preserves the tab when refreshing the page or going
through browser history

My hypothesis is that those missing files are making the swh-docs build fail.
That's the only difference i see between those swh.web folders and the rest.

Origin URLs were printed unsanitized

This is more manageable than handling it manually with URL fragments
(which repeatedly breaks when adding new tabs).

This is IMO more manageable than handling it manually with URL fragments
(which repeatedly breaks when adding new tabs).

A future commit will do this for Add Forge Now, too.

The Alegreya font we are using ships some ligatures producing confusing
text rendering, for instance the ligatures for `~` and some characters.

So disable font common ligatures with CSS.

The use of nodemon is no longer needed as source files are
already watched by django and webpack development servers
automatically reloading backend and frontend parts of the
web application.

There is an incompatibility between latest django-stubs release (1.10.0)
and current release of djangorestframework-stubs.

So temporarily pin django-stubs to < 1.10.0 until the issue is fixed.

This introduces a checkbox to allow users to filter their own requests. It's turned on
by default. The checkbox is not shown when connected anonymously.

Either browsing anonymously or unchecking the box (when connected) allows to browse all
requests.

This also unifies the rendering with the save code now view:
- same datatable layout
- the spinner logo during computation

Related to T4011

Maintain selected tab in add-forge-now create view.
Add URL hash for the help tab.
Improve cypress tests for the tab change.

Related to T4050

Related to T4087

This will allow to reuse that part inside the add-forge-now form as well.

Related to T4011

This makes sure we use the right keycloak login link when deployed on staging and
production webapps. This does not change anything for docker and dev makefile targets.

Related to T4075

Use dedicated functions in archive module to get an origin visit by id
or by date.

Only get all visits as a fallback when one needs to get an origin visit
by snapshot.

Related to T4075